design-review-cyclelisted

# Design Review Cycle Submit design documents, implementation plans, or specifications for peer review through the LLM gateway. Track review iterations until approval. ## Dispatch Defaults Apply these on every dispatch unless the caller has explicitly overridden a rule in the current turn: 1. **Omit `model`** — let the gateway use its configured default per CLI. 2. **`approvalStrategy:"mcp_managed"`** is the skill dispatch default (the gateway schema default is `"legacy"`). For Codex, also pass `fullAuto:true` when it must read files or run commands. 3. **No wallclock timeout; poll every 60 s** — `idleTimeoutMs` is a separate no-output safeguard. 4. **Iterate until unconditional APPROVED** (review dispatches only) — every review prompt must end with "End with APPROVED or NOT APPROVED with findings." Loop: dispatch → parse verdict → on `NOT APPROVED` or conditional, revise + re-submit → repeat. Escalate after 3 rounds. This rule does **not** apply to pure implementation or non-review analysis dispatches. ## When to Use - Before implementing a complex feature (review the plan first) - After writing a specification or design document - When a development process requires peer review before code - For architecture decisions that affect multiple components ## Review Workflow ### Step 1: Prepare the Review Request Write a clear review request that includes: - What document to review (file path) - What kind of review (design, spec, plan, architecture) - Specific concerns or