implement is the default coding workflow for a single change. It runs a shared ValidationLoop: implement the requested change, validate it, review it, and feed failures back into another iteration.
Inputs
| Input | Type | Default |
|---|---|---|
prompt | string | "Implement the requested change." |
How It Runs
- An implementation agent works from the prompt.
- A validation agent checks the repo state.
- Reviewer agents inspect the result.
- The orchestrator feeds failed validation output and reviewer rejection notes back into the next implementation pass.
- The loop stops after validation passes and at least one reviewer 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 for each 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 a multi-milestone effort.
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 the process is interrupted, resume withup --resume and finished iterations are not repeated. The validation loop runs up to 3 iterations, stopping once validation passes and at least one reviewer approves.