review-driven-developmentlisted

# 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 When the user provides an issue number: 1. **Fetch issue details** — auto-detect platform: - GitHub: `gh issue view <NN> --json title,body,labels,assignees` - GitLab: `glab issue view <NN>` - If neither works, ask the user for the issue URL 2. **Research the codebase** — launch Explore agents to understand: - What code is involved - What patterns exist in the codebase - What reference repos or docs are relevant (check CLAUDE.md, memory) 3. **Enter plan mode** to present the implementation plan ## Phase 2: Plan + Worktree The plan MUST include: - **Worktree setup**: directory path, branch name (read