implement is archived (not installed by init): copy it from examples/init-pack/ with its dependency closure, or ask create-workflow to build an equivalent. It is the default coding workflow for a single change: a shared ValidationLoop implements, validates, reviews, and iterates on failures.
The implement UI streams each stage (implementation, validation, and the reviewer panel's synthesized verdict) as the build → validate → review loop runs.
Inputs
How It Runs
- An implementation agent works from the prompt.
- A validation agent checks the repo state.
- A panel of reviewer agents inspects the result; a moderator synthesizes them into one verdict.
- The orchestrator feeds failed validation output and review feedback into the next implementation pass.
- The loop stops after validation passes and the synthesized review verdict approves, or after 3 iterations.
Output Shape
implement commits changes directly to the working tree; the run log records the validation result and reviewer feedback per iteration.
Use it when
- You already know what to build and want a build, validate, review loop enforced.
- The change is a single, focused unit, not multi-milestone.
Use something else when
- The change needs context first: use
research-plan-implementorplan. - The work spans many independent units: split it with
tickets-create, then runkanban. - The scope is too broad for one loop: use
mission.
Resume & retry
The run is durable: if interrupted, resume withup --resume; finished iterations are not repeated (see the loop’s stop condition above).