| name | sup-coding |
| description | Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish) |
| supervisor | {"workflow":"coding","required_capabilities":["coding","shell","reasoning"]} |
When to use
When a task is classified as code_change, bug_fix, or refactor.
Operating rules
- Always run inside an isolated branch/worktree.
- Always run formatter, linter, and tests before declaring success.
- Verification evidence: at minimum one passing test or one confirmed diff.
- Prefer test-driven development: write a failing test, then make it pass.
- Keep commits small and logically scoped.
Stop conditions
- All planned changes implemented.
- Verification passes (build, tests, lint, format).
- Reviewer notes are addressed.