subagent-review-cycleslisted

# Subagent Review Cycles ## When to invoke - About to dispatch a sub-agent to draft a technical document / design section. - The first version of a document is ready and a Code Reviewer should audit technical correctness. - User asks "how many review rounds", "should Code Reviewer run CLI", "what counts as rejection". ## The triad | Role | Job | |---|---| | **Leader** (main agent) | Dispatch, integrate review results, accept / reject, communicate with the user | | **Developer** (subagent) | Draft / revise document sections; works after Leader replies with rejection. (The Developer role is often dispatched as a Software Architect sub-agent type when the task is architectural in nature, but the role name remains "Developer".) | | **Code Reviewer** (subagent) | Audits Developer output for technical / API correctness and logic gaps; CLI is forbidden for probing API/runtime behavior (build, run, simctl, trial-and-error); read-only search (grep, rg, git log, git show) is allowed | The Leader **never** writes the implementation / drafts a section directly — that's the Developer's job. The Leader **never** does the review either — that's the Code Reviewer's job. ## Round structure ``` round N: Leader → Developer: dispatch (scope + skills + inputs + return format + criteria) Developer → Leader: draft Leader → Code Reviewer: dispatch (review criteria + must use WebSearch, no CLI) Code Reviewer → Leader: BLOCKER / MAJOR / MINOR list Leader: ACCEPT / REJECT each item wit