with one click
implement
Implement a piece of work based on a spec or set of tickets.
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.
Menu
Implement a piece of work based on a spec or set of tickets.
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
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | implement |
| description | Implement a piece of work based on a spec or set of tickets. |
| disable-model-invocation | true |
Implement the work described by the user in the spec or tickets.
Before coding, claim the ticket (mise run issue:claim -- <n>) so it carries
in-progress. Do not start a ticket that is already claimed. See
docs/agents/issue-workflow.md.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /code-review to review the work.
Commit your work to the current branch.
When opening the PR, the body must include Closes #<ticket> (e.g.
Closes #13). A title like (#13) is not enough — GitHub only auto-closes on
merge when the body uses a closing keyword. Infra/docs PRs with no product
ticket may use No-ticket: true instead.