coder-eval-implement-plan

Context

• Current git status: !git status --short
• Current branch: !git branch --show-current
• Recent commits: !git log --oneline -5

Implement Plan

Implement an approved plan produced by /coder-eval-create-plan phase by phase, verifying and reviewing each phase before moving on, then run one cross-cutting review of the whole change. The plan is your contract: it carries, per phase, a Risk tag, Changes, Edge Cases, Tests to Write, Tests to Run (scoped commands), and Acceptance Criteria, plus a global Master Acceptance Checklist, Patterns to Mirror (real code snippets), and a Confidence Score. Drive off those — do not re-derive what the plan and CLAUDE.md already specify. The plan path is: $ARGUMENTS

If no plan path was provided, ask for one.

When to use this

This command is for multi-phase plans where phases build on each other and the cost of a wrong turn is high. For a single trivial change (one file, a rename, a typo, a one-line fix), skip the ceremony below — make the change, run the relevant scoped test, and stop. Do not spawn review sub-agents for work a human would eyeball in ten seconds. (If the plan's Confidence Score is below 7, stop — per /coder-eval-create-plan it isn't ready; surface that instead of implementing.)

The loop

Everything below expands this core loop. Hold it in your head:

pre-flight (understand plan + Patterns to Mirror, learn conventions, capture <start-sha>, build task list + findings file)
for each phase, in order:
    implement   → write the phase's "Tests to Write" first for new behaviour, then the code
    verify      → Stage 1: the phase's "Tests to Run" + scoped lint must pass
    review      → Stage 2: spec-compliance, then (risk-scaled) quality
    commit      → conventional message with a progress counter
final review of the whole change → fix → tick Master Acceptance Checklist → summary

Complete one phase fully before starting the next. Stay within the plan's scope — do not refactor or extend beyond what it specifies.