What it does
Use it for implementation, debugging, architecture analysis, refactors, CI issues, PR work, and any task where the agent must navigate a real codebase responsibly.
How it works
- Starts with repo orientation, ownership discovery, and the proof path before writing code.
- Routes work through the right mode: direct execution, subagents, review, architecture analysis, or release flow.
- Ends with verification and explicit completion status rather than vague progress claims.
Best for
- • Cross-cutting software changes
- • PRD-to-implementation execution
- • Repository-grounded code review and debugging
Expected outputs
- • Scoped implementation plan
- • Verified code changes or findings
- • Clear completion, concern, or blocker report