Menu
Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Check whether this card's code meets the acceptance criteria
Run a quick UX/UI workshop using ASCII-art sketches
Write automated tests for unticked scenarios in this card's test cases
Review code changes on this card for likely bugs, regressions, and missed edges
Cherry-pick post-merge commits onto a new follow-up branch
Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.
| name | spec-review |
| description | Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact |
| label | Review spec |
| pill-order | {"specifying":3} |
| workhorse-version | 0.2.0 |
If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following .agents/docs/card-context.md.
Read the spec files in .workhorse/specs/ that relate to this card and review them as if you were seeing them for the first time. Set aside the earlier conversation context and check that the specs stand on their own.
Look for:
.agents/docs/spec-format.mdBe specific and constructive. Reference exact criteria when noting issues. Post findings as a structured message the user can work through with you — don't silently edit the specs in response to your own review.