Review-Driven Development

A complete issue-to-merge workflow where the iterative review cycle is the core driver. The PR/MR doesn't just get created — it gets reviewed N rounds with fixes until the verdict is APPROVE.

Announce at start: "Using review-driven-development to implement issue #NN through the full review cycle."

Overview

Issue → Research → Plan → Worktree → Implement → Test → PR/MR → Review ⟲ Fix → APPROVE → Merge
                                                                 ↑_____________↩ (repeat until clean)

The review cycle (Phase 5) is what separates this from a simple "code and push" workflow. Every PR/MR goes through at least one structured review round, with findings posted directly to the PR/MR. Issues get fixed, re-reviewed, and the cycle repeats until the verdict is APPROVE.

Phase 1: Issue Research