implement

Workspace Resolution

1. If $ARGUMENTS specifies a project name or todo, parse accordingly
2. Otherwise, use the most recently modified directory under workspaces/ (excluding instructions/)
3. If no workspace exists, ask the user to create one first
4. Read all files in workspaces/<project>/briefs/ for user context (this is the user's input surface)

Phase Check

• Read files in workspaces/<project>/todos/active/ to see what needs doing
• Read files in workspaces/<project>/todos/completed/ to see what's done
• If $ARGUMENTS specifies a specific todo, focus on that one
• Otherwise, pick the next active todo
• Reference plans in workspaces/<project>/02-plans/ for context
• If any file in briefs/ was modified after specs/_index.md, STOP — briefs changed since analysis. Flag for user decision: re-run /analyze or acknowledge the brief change.

Execution Model

This phase executes under the autonomous execution model (see rules/autonomous-execution.md). Implementation is fully autonomous — agents execute in parallel, self-validate through TDD, and converge through quality gates. The human observes outcomes but does not sit in the execution loop. Pre-existing failures are fixed, not reported (zero-tolerance). Agent-to-agent delegation (reviewer, security-reviewer) is autonomous, not human-gated.

Workflow

NOTE: Run /implement repeatedly until all todos/active have been moved to todos/completed

Wave boundary (MUST): /implement runs the CURRENT wave (one value-ranked milestone-group per rules/wave-loop.md MUST-1). At wave completion, STOP and run the inter-wave gate (rules/wave-loop.md MUST-2: G1 /redteam to convergence → G2 lightweight learning-capture → G3 update specs + remaining todos → G4 re-value-rank) BEFORE starting the next wave. G1 counts a "clean round" ONLY when every dispatched reviewer genuinely ran (rules/wave-loop.md MUST-3 evidence-gate — an errored / empty / timed-out / throttled reviewer is zero evidence, re-run it; a "0 findings" tally from a reviewer that never ran is false convergence that feeds an un-reviewed base into the next wave), and each boundary's convergence / codify / re-rank claim MUST cite a durable receipt (rules/wave-loop.md MUST-5 — journal entry / commit SHA, never a self-attested "converged ✓"). Do NOT drain all of todos/active/ across wave boundaries — draining past the gate is the deferred-verification failure the wave-loop closes. A single-milestone serial project (one convergence surface) runs as one wave; its terminal /redteam is its only gate.