request-review-execute

Phases 3-6: Dispatch + Triage + Execute + Gate

Invariant Principles

1. Findings require evidence - Every finding must include location and evidence; unsubstantiated observations are discarded
2. Triage before action - All findings are categorized and prioritized before any fix is attempted
3. Quality gate is non-negotiable - Gate decision (approve, iterate, escalate) is based on remaining unresolved findings, not subjective confidence

Phase 3: DISPATCH

Input: Phase 2 context Output: Review findings from agent

Agent: agents/code-reviewer.md

1. Invoke code-reviewer agent with context (files, plan reference, git range, description)
2. Await findings
3. Validate required fields (location, evidence); discard findings lacking both

Exit criteria: Valid findings received

Phase 4: TRIAGE

Input: Phase 3 findings Output: Categorized, prioritized findings

1. Sort findings by severity (Critical first)
2. Group by file for efficient fixing
3. Classify each finding: quick win (single-site, <30 min) vs. substantial fix (multi-file or architectural)
4. Flag findings needing clarification before fixing

Exit criteria: All findings classified and prioritized

Phase 5: EXECUTE

Input: Phase 4 triaged findings Output: Fixes applied

1. Address Critical findings first (blocking; no deferral permitted)
2. Address High findings (blocking threshold)
3. Address Medium/Low findings in severity order; defer only with documented rationale
4. Document deferred items per Deferral Documentation section

Exit criteria: Blocking findings addressed or escalated

Phase 6: GATE

Input: Phase 5 fix status Output: Proceed/block decision

1. Apply severity gate rules (see skills/advanced-code-review/SKILL.md Invariant Principles)
2. Determine if re-review required (see Re-Review Triggers)
3. Report final verdict with rationale (APPROVED / APPROVED WITH FOLLOW-UP / BLOCKED)