Feature development
Use this workflow for a meaningful repository change. Compress or skip phases when the request is genuinely trivial.
- Discover — Restate the requested outcome and identify hard constraints.
- Explore — Inspect the real entry points and call sites. Spawn a
code-exploreronly for a focused, independent question, then wait for it. - Clarify — If an unresolved choice would materially change the result, stop and ask a concrete question. Otherwise state the safe assumption.
- Design — Reuse the closest existing module. Spawn
code-architectonly when the change has a genuine architectural choice, then wait for it. - Implement — The root agent alone edits files. Keep the diff focused and preserve unrelated user changes.
- Verify — Run the narrowest integration-level check that would fail if the behavior regressed.
- Review — Spawn
code-revieweragainst the completed diff, wait for it, and repair confirmed high-impact findings before summarizing.
Never stage, commit, publish, or deploy unless the user explicitly requests it.