Show Your Work
From its catalog listing
An evidence board for a change's acceptance criteria: which requirements your agent actually tested, what the imported results say, whether they still match the code, and whether you signed off. Point it at the requirements you already have (a ticket, bug report or spec in Markdown) and it shows four separate statuses per requirement, never merged into one green check: coverage (is a test linked?), outcome (latest imported JUnit run), freshness (tracked files changed since?) and human review. For review, click a requirement and then a linked test to see that test's source and its own diff against the base branch (new, changed or unchanged), plus the change under review. The agent links tests and imports reports from wherever they ran (terminal, Docker, CI); it has no tool to accept or reject. Sign-off comes from the Desktop page, /syw or hermes syw. Five tools (syw_board, syw_link, syw_import, syw_run_detail, syw_test_evidence), a /syw command, a hermes syw CLI, a Desktop page and a workflow skill.
Good to know before installing
runs no tests and makes no network or model calls; reads syw.toml, the criteria file, tracked files (to hash them) and JUnit XML inside the project folder (paths outside it and symlinks refused), runs read-only git (rev-parse, merge-base, diff, show, ls-files) in the project folder when you open a test's evidence or the change panel, stores links, results, hashes and reviews in SQLite under the profile's plugin-data, and writes show-your-work-review.md into the project only when you export.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install show-your-work - Said no? Turn it on later:
hermes plugins enable show-your-work - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Coding & developer tools
- Maintained by
- kenpritchard (Community)
- Needs
- No API keys declared
- Adds tools
syw_boardsyw_linksyw_importsyw_run_detailsyw_test_evidence- Works on
- linux, macos, windows
- Needs Hermes
- 0.23.0 or newer
- Version
- 0.2.1
- In the catalog
- 2026-11-11
Known issues (from its catalog listing)
- Sign-off is human-only through the plugin's tools, but `hermes syw accept` is an ordinary CLI command, so an agent with a terminal tool could run it (recorded as human:cli). The bundled skill tells agents never to.
- With a remote backend (Docker, SSH), `hermes plugins update` on the server updates only the agent half; update the Desktop page from Desktop (Install from Git / Update with Desktop ticked) and Reload desktop plugins. After installing or updating, restart the dashboard backend so the page's API and the plugin host load the new code.
- On native Windows, `hermes plugins install` can fail with WinError 32/5 (Hermes installer, #136120); docs/USAGE.md has a manual-clone workaround.
- Finding a test's source from its JUnit id is a best guess (Java/Kotlin/Scala/Groovy, Python, Go, simple JS); when it can't, the panel says so.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in coding & developer tools
All coding & developer tools plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher