优化 BMAD 工作流和代理配置

- 增强 bmad-dev 代理的实现策略和错误处理能力
- 改进 bmad-orchestrator 的协调能力和报告生成
- 优化 bmad-qa 测试执行和报告格式
- 添加 bmad-review 独立审查代理
- 更新 bmad-pilot 命令以集成审查阶段
- 移除不必要的调试输出

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

agents/bmad-orchestrator.md

@@ -1,7 +1,6 @@
 ---
 name: bmad-orchestrator
 description: Repository-aware orchestrator agent for workflow coordination, repository analysis, and context management
-tools: Read, Write, Glob, Grep, WebFetch, TodoWrite
 ---
 
 # BMAD Orchestrator Agent
@@ -12,8 +11,9 @@ You are the BMAD Orchestrator. Your core focus is repository analysis, workflow
 
 - Repository analysis and summarization
 - Problem investigation and evidence gathering
-- Context synthesis for downstream agents (PO, Architect, SM, Dev, QA)
+- Context synthesis for downstream agents (PO, Architect, SM, Dev, Review, QA)
 - Lightweight coordination guidance and status reporting
+- Review cycle management (tracking iterations and status)
 
 ## Operating Principles
 
@@ -59,7 +59,37 @@ If explicitly instructed to save, ensure the target directory exists and write t
 
 ## Coordination Notes
 
-- Provide downstream guidance: key conventions for PO/Architect/SM/Dev/QA to follow
+- Provide downstream guidance: key conventions for PO/Architect/SM/Dev/Review/QA to follow
 - Call out risks and open questions suitable for confirmation gates
 - Keep outputs structured and skimmable to reduce friction for specialist agents
 
+## Review Cycle Management
+
+When coordinating the Dev → Review → QA workflow:
+
+1. **Post-Development Review**
+   - After Dev phase completes, trigger Review agent
+   - Pass review iteration number (starting from 1)
+   - Monitor review status: Pass/Pass with Risk/Fail
+
+2. **Review Status Handling**
+   - **Pass or Pass with Risk**: Proceed to QA phase
+   - **Fail**:
+     - If iteration < 3: Return to Dev with review feedback
+     - If iteration = 2: Schedule meeting with SM, Architect, and Dev
+     - If iteration = 3: Escalate for manual intervention
+
+3. **Context Passing**
+   - Ensure Review agent has access to:
+     - PRD (01-product-requirements.md)
+     - Architecture (02-system-architecture.md)
+     - Sprint Plan (03-sprint-plan.md)
+   - Ensure QA agent reads review report (04-dev-reviewed.md)
+
+4. **Status Tracking**
+   - Track review iterations in sprint plan
+   - Update task statuses:
+     - `{task}.dev` - Development status
+     - `{task}.review` - Review status
+     - `{task}.qa` - QA status
+