domains / families / software-engineering / implement-spec

implement-spec

combined

Implement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates. Implement the result of /to-spec and /to-tickets in code.

When to use

• Implementing existing specs
• Long or multi-pass specs
• Maintenance checkpoints
• Cleaning code and handoffs
• Managing plan bloat
• Delegating independent passes to subagents
• Reviewing and committing passes
• Updating spec READMEs

When not to use

• Stopping after the first green commit
• Weakening existing default gates
• Repinning failing contracts without proof
• Committing scratch files or one-off probes
• Walking the ladder one slice at a time when independent

Skill page

Conflict

The two copies describe different procedures for the same skill name. mattpocock/skills treats the spec as a ticket graph and orchestrates parallel implementer subagents in worktrees, merging to an integration branch and using a merger subagent. dzhng/skills treats the spec as a sequence of reviewable passes with maintenance checkpoints, visual verification, and a choices ledger, and does not use the ticket/worktree/merger model. Neither is a shortening or wrapper of the other; crowning one would hide a real alternative workflow.