implement

name	implement
description	Execute a checked-in implementation plan end-to-end using parallel agents. Use when a spec and plan exist in .plans/ and you're ready to build.

Implement Plan

/implement — read spec and plan from .plans/, execute phases /implement .plans/<date>-<name>.md — explicit plan path /implement specs/<name>.md — spec path: generate the plan from this spec first, save it to .plans/, then execute

Prerequisites

Agent tool, /review, /verify, /qa, /debug, /gates.

Input

$ARGUMENTS = path to a plan file, or a spec file to generate the plan from. If omitted: use the most relevant spec on the branch, generate a plan, save to .plans/, proceed.

Fallback — no spec: check .plans/context.md first; if present, generate a plan from it. Otherwise: prompt the user — run /design or continue without spec? See REFERENCE.md §1 for the full fallback chain.

Process

Step 1: Read & Analyze Plan

• Identify phases, dependencies, parallelization opportunities (sequential vs. parallel).
• Findings reconciliation: Cross-reference every finding ID (CC-01, V-15) from any findings doc against plan text; report gaps.
• Shared-infrastructure scan: Identify files in multiple phases; flag conflicts (must serialize or designate owner). See REFERENCE.md §5.

Step 2: Load Spec Context

Read specs/CONSTITUTION.md + relevant specs (grep **Code:** frontmatter). Build spec context block for every subagent. See REFERENCE.md §4.

Step 3: Assess Current State

Check git status, branch, existing worktrees, prior phase commits.

Step 4: Create Task Tracking

Build task list from plan phases; mark already-completed work done.

Step 4.5: Assess Model Selection

Read REFERENCE.md §3 for Opus vs. Sonnet guidance.

Step 5: Execute Each Phase

A. Dispatch Agents — parallel for independent tasks; see REFERENCE.md §5.

B. Collect Results — wait for all agents; review summaries.

B2. Cross-Agent Consistency Check — verify cross-surface contract consistency; see REFERENCE.md §7.

C. Verify Phase Gate — build → tests → AC coverage → surface-specific verify/qa → review. See REFERENCE.md §6. Fix before advancing.

D. Review — invoke /review (reviewer sees diff + constitution + ACs only). Fix issues.

E. Commit — git add specific files; commit per REFERENCE.md §8.

F. Advance — move to next phase after commit. Update task tracking.

Step 6: Mandatory Tail — Full Verification Sequence

A. Gates — /gates B. Verify — /verify extension|tui|cli|mcp per changed surfaces C. QA — /qa extension|cli|mcp|tui per changed surfaces D. Review — /review final comprehensive review E. Converge — if critical/important findings: gates→review→fix loop (max 5 cycles) F. Final State Check — git status --porcelain produces no output (no uncommitted or untracked files); all phases committed. G. Submit — proceed IMMEDIATELY to /pr; do not stop to summarize