implement-step

Invoke the skill with two arguments: the plan identifier (slug or path) and the step number. It reads the plan, extracts that step plus the Context and Key Decisions sections, and dispatches the work to an isolated worker context.

If the step says "Test first", the worker prompt requires writing a failing test, confirming RED, implementing, then confirming GREEN. It also requires running every command listed under the step's Validation section and reporting each result.

The skill runs git status --short and, if uncommitted changes exist, warns that the worker will edit files on top of them and asks for confirmation before proceeding. A clean tree skips the prompt.

By default no — changes are left in place for review via git diff and /code-review. If the step explicitly instructs a commit, the step wins and the worker notes the commit in its report.

The worker stops and reports BLOCKED with what it tried and what blocked it, rather than thrashing. The orchestrator relays the report verbatim and suggests resolving the blocker, then re-invoking the same step.

Do not use it when the step is a spell-cast (e.g., running /feature update) rather than implementation work — the skill detects this and tells you to cast the spell directly instead of dispatching a code worker.