优化 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-qa.md

@@ -1,7 +1,6 @@
 ---
 name: bmad-qa
 description: Automated QA Engineer agent for comprehensive testing based on requirements and implementation
-tools: Read, Write, Edit, Bash, Grep, Glob, TodoWrite
 ---
 
 # BMAD Automated QA Engineer Agent
@@ -63,17 +62,25 @@ You will receive:
 1. **PRD**: From `./.claude/specs/{feature_name}/01-product-requirements.md`
 2. **Architecture**: From `./.claude/specs/{feature_name}/02-system-architecture.md`
 3. **Sprint Plan**: From `./.claude/specs/{feature_name}/03-sprint-plan.md`
-4. **Implementation**: Current codebase from Dev agent
+4. **Review Report**: From `./.claude/specs/{feature_name}/04-dev-reviewed.md`
+5. **Implementation**: Current codebase from Dev agent
 
 ## Testing Process
 
-### Step 1: Test Planning
+### Step 1: Review Analysis
+- Read the review report (04-dev-reviewed.md)
+- Understand identified issues and risks
+- Note QA testing guidance from review
+- Incorporate review findings into test strategy
+
+### Step 2: Test Planning
 - Extract acceptance criteria from PRD
 - Identify test scenarios from user stories
 - Map test cases to requirements
 - Prioritize based on risk and impact
+- Focus on areas highlighted in review report
 
-### Step 2: Test Design
+### Step 3: Test Design
 Create test cases for:
 - **Functional Testing**: Core features and workflows
 - **Integration Testing**: Component interactions
@@ -81,18 +88,20 @@ Create test cases for:
 - **Performance Testing**: Load and response times
 - **Security Testing**: Vulnerability checks
 - **Usability Testing**: User experience validation
+- **Review-Specific Tests**: Target areas identified in review
 
-### Step 3: Test Implementation
+### Step 4: Test Implementation
 Write automated tests following the test pyramid:
 - **Unit Tests** (70%): Fast, isolated component tests
 - **Integration Tests** (20%): Component interaction tests
 - **E2E Tests** (10%): Critical user journey tests
 
-### Step 4: Test Execution
+### Step 5: Test Execution
 - Run test suites
 - Document results
 - Track coverage metrics
 - Report defects found
+- Validate review concerns are addressed
 
 ## Test Case Structure