Menu
Lightweight bugfix workflow. No full spec needed — just find the root cause, fix it, add a regression test, and commit. Use for bugs, not for new features.
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
| name | spec-fix |
| description | Lightweight bugfix workflow. No full spec needed — just find the root cause, fix it, add a regression test, and commit. Use for bugs, not for new features. |
| argument-hint | <bug description or issue number> |
Reproduce: Understand the bug from the description. Search the codebase for related code.
Trace: Follow the code path to find the root cause. Use Explore agents if the scope is unclear.
Present findings to user:
file.rs:123 — here's what happens: ..."Check specs: Search docs/specs/ for specs that cover the affected code. If the fix changes behavior defined in a spec, flag it: "This fix affects spec X — AC-N needs to be updated."
Ask for confirmation before fixing.
Write the regression test first — it should fail before the fix and pass after
Fix the bug — minimal change, don't refactor surrounding code
Run cargo clippy && cargo test (and npm run check if frontend)
Update affected specs — if the fix changes behavior covered by a spec, update the relevant ACs to match the corrected behavior
Show the user: diff summary + test results + spec changes (if any).
fix: <what was broken>Fixes #<number>Ask for confirmation before committing.
/spec insteadBranch: !git branch --show-current
Recent commits: !git log --oneline -5 2>/dev/null
Reverse-engineer a spec from existing code. Explores the codebase for a given area/feature and generates a spec that documents what's already implemented. Use to create specs for legacy code or to establish a baseline.
Implement a feature based on an existing spec from docs/specs/. Reads the spec, implements in 3 gated phases (contract, code, verify+commit). Use after /spec.
Collaboratively create or update a feature spec. Creates a new spec if none exists, or updates an existing one when requirements change. Use for new features and significant changes — not for bugfixes.
Verify a spec against the codebase and update its status. Without argument runs a general project consistency check. Use "all" for full audit before releases.