Implement Plan With Subagents

Orchestrate the autonomous, plan-driven, multi-subagent implementation of a plan artifact. This skill is the orchestrator role: it does not write code itself — it reads the plan artifact READ-ONLY, walks the numbered task list in plan order, dispatches an implementer subagent for each task, dispatches a plan-compliance reviewer subagent (first pass), dispatches a code-quality reviewer subagent (second pass), respawns a NEW implementer subagent on review failure, re-reviews every fix before advancing, commits per orchestration cycle, reports a four-state status per plan task, and emits a single immutable implementation report record on the way out. By default it does not pause for clarifying questions at each step or ask before committing, but it honors an invocation that asks it to check in or work through the tasks interactively; it does not rewrite history.

Subagent Capability Precondition

This skill REQUIRES subagent capability (e.g., a runtime primitive that lets the orchestrator spawn an independent subagent with its own context window and have it write files to disk before replying with an acknowledgment). The orchestrator role this skill defines is meaningful only when implementer and reviewer subagents are real, separate-context dispatches.

This skill does NOT fall back to inline execution. There is no "if subagents are unavailable, do it yourself" branch. The orchestrator does not write code in-session, does not run reviews in-session, and does not collapse the three subagent roles back into a single agent — that defeats the dual-reviewer separation and the fresh-context-per-fix discipline. Subagent topology is a precondition of this skill, not a feature toggle. If the runtime does not support subagents, stop and tell the user this run cannot proceed.

No Worktree Isolation

The subagents this skill dispatches run sequentially on the SAME working tree as the orchestrator. This skill does NOT use git worktree add isolation, parallel-worktree topology, or separate per-subagent working directories. Each subagent's writes to the working tree are observable to the next subagent — the plan-compliance reviewer reads what the implementer just wrote; the next implementer (on a fix iteration) reads the previous implementer's diff and the reviewer's findings; the code-quality reviewer reads the same final post-fix state. Subagents run sequentially, on the same tree, in the order this skill's ## Workflow defines.

No parallel implementer dispatch. No per-task worktree branch. The orchestration cycle (one task) ends with one commit on the current working tree; the next cycle starts from that committed state on the same tree.

Inputs

This skill accepts a plan artifact path. The plan artifact lives in a lineage folder under the thread root: