cc-devflow 2.5.0 → 4.1.1

package/.claude/commands/{flow-dev.md → flow/dev.md}

@@ -1,6 +1,6 @@
 ---
 name: flow-dev
-description: 'Execute development tasks following TDD order. Usage: /flow-dev "REQ-123" [--manual] [--max-iterations N]'
+description: 'Execute development tasks following TDD order. Usage: /flow-dev "REQ-123" [--manual] [--max-iterations N] [--team] [--agents N]'
 scripts:
   prereq: .claude/scripts/check-prerequisites.sh
   check_tasks: .claude/scripts/check-task-status.sh
@@ -8,6 +8,9 @@ scripts:
   validate_constitution: .claude/scripts/validate-constitution.sh
   verify_gate: .claude/scripts/verify-gate.sh
   setup_loop: .claude/scripts/setup-ralph-loop.sh
+  team_init: .claude/scripts/team-dev-init.sh
+  parse_tasks: .claude/scripts/parse-task-dependencies.js
+  detect_conflicts: .claude/scripts/detect-file-conflicts.sh
 skills:
   tdd: .claude/skills/flow-tdd/SKILL.md
   verification: .claude/skills/verification-before-completion/SKILL.md
@@ -55,25 +58,28 @@ NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
 
 ## User Input
 ```text
-$ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N]"
+$ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N] [--team] [--agents N]"
 ```
 
 - **REQ_ID**: 未提供时从当前分支或 `DEVFLOW_REQ_ID` 推断
 - **--task T###**: 指定起始任务（从该任务开始执行）
 - **--manual**: Manual模式，遇错停止等待人工修复（向后兼容）
 - **--max-iterations N**: Autonomous模式最大迭代次数（默认10）
+- **--team**: Team模式，启用多 Agent 并行执行 [NEW: v4.7]
+- **--agents N**: Team模式下的 Agent 数量（默认3，范围2-5）[NEW: v4.7]
 
 **默认行为**: Autonomous模式（自动重试直到完成）
 
 ### 运行模式对比
 
-| | Manual模式 | Autonomous模式（默认） |
-|--|------------|----------------------|
-| 触发方式 | `--manual` | 默认（或指定 `--max-iterations`） |
-| 遇到错误 | 停止，等待人工修复 | 自动重试，记录 ERROR_LOG.md |
-| 注意力刷新 | Protocol 2（每任务） | Protocol 2 + Protocol 3（每迭代） + Protocol 4（遇错） |
-| 适用场景 | 复杂需求需人工判断 | 清晰需求可无人值守 |
-| 退出条件 | 任务失败可停止 | 迭代直到完成或达到上限 |
+| | Manual模式 | Autonomous模式（默认） | Team模式 [NEW] |
+|--|------------|----------------------|----------------|
+| 触发方式 | `--manual` | 默认 | `--team` |
+| 遇到错误 | 停止，等待人工修复 | 自动重试 | 分布式重试 |
+| 并行执行 | 否 | 否 | 是（多 Agent） |
+| 注意力刷新 | Protocol 2 | Protocol 2+3+4 | 每 Agent 独立 |
+| 适用场景 | 复杂需求 | 清晰需求 | 大量并行任务 |
+| 退出条件 | 任务失败可停止 | 迭代直到完成 | 所有 Agent 完成 |
 
 **示例**:
 ```bash
@@ -82,6 +88,8 @@ $ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N]"
 /flow-dev "REQ-123" --manual             # Manual模式，遇错停止
 /flow-dev "REQ-123" --task T005          # 从 T005 开始（Autonomous模式）
 /flow-dev "REQ-123" --task T005 --manual # 从 T005 开始（Manual模式）
+/flow-dev "REQ-123" --team               # Team模式，3 个 Agent 并行
+/flow-dev "REQ-123" --team --agents 5    # Team模式，5 个 Agent 并行
 ```
 
 ## 执行流程
@@ -89,9 +97,10 @@ $ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N]"
 ### 阶段 1: Entry Gate
 ```
 1. 解析参数
-   → Parse: REQ_ID, --task, --manual, --max-iterations
+   → Parse: REQ_ID, --task, --manual, --max-iterations, --team, --agents
    → If REQ_ID not provided: run {SCRIPT:prereq} --json --paths-only
    → Determine mode:
+      • --team flag present → Team mode
       • --manual flag present → Manual mode
       • Otherwise → Autonomous mode (default max_iterations = 10)
 
@@ -115,6 +124,12 @@ $ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N]"
    → 任务格式 `- [ ] T### [P?] [US?] Description (path)`
 
 4. 模式初始化
+   → If Team mode:
+      • Run: {SCRIPT:team_init} init "${REPO_ROOT}" "${REQ_ID}" ${NUM_AGENTS}
+      • Analyze tasks: {SCRIPT:team_init} analyze "${REPO_ROOT}" "${REQ_ID}"
+      • Check conflicts: {SCRIPT:team_init} conflicts "${REPO_ROOT}" "${REQ_ID}"
+      • Assign tasks: {SCRIPT:team_init} assign "${REPO_ROOT}" "${REQ_ID}" ${NUM_AGENTS}
+      • Log to EXECUTION_LOG.md: "Starting Team mode with N agents"
    → If Autonomous mode:
       • Run: {SCRIPT:setup_loop} "${REQ_ID}" --max-iterations ${MAX_ITERATIONS}
       • Creates .claude/ralph-loop.local.md (state file for Stop Hook)
@@ -158,6 +173,84 @@ $ARGUMENTS = "REQ_ID? [--task T###] [--manual] [--max-iterations N]"
 
 ### 阶段 3: 执行循环
 
+**Team 模式循环** (--team) [NEW: v4.7]:
+```
+┌──────────────────────────────────────────────────────────────────┐
+│ Team Mode Execution Flow                                          │
+├──────────────────────────────────────────────────────────────────┤
+│                                                                   │
+│  1. 任务分析与分配                                                 │
+│     → Run: {SCRIPT:team_init} analyze "${REPO_ROOT}" "${REQ_ID}"  │
+│     → Run: {SCRIPT:team_init} conflicts "${REPO_ROOT}" "${REQ_ID}"│
+│     → Run: {SCRIPT:team_init} assign "${REPO_ROOT}" "${REQ_ID}" N │
+│                                                                   │
+│  2. 并行执行                                                       │
+│     → 每个 Agent 独立执行分配的任务                                │
+│     → 文件冲突的任务分配给同一 Agent 串行执行                       │
+│     → 无冲突的任务可并行执行                                       │
+│                                                                   │
+│  3. 任务完成处理                                                   │
+│     → TeammateIdle Hook 验证任务完成                               │
+│     → 验证通过 → 标记完成，分配下一任务                            │
+│     → 验证失败 → 继续修复                                          │
+│                                                                   │
+│  4. 阶段转换                                                       │
+│     → 当前阶段所有任务完成 → 进入下一阶段                          │
+│     → 重新分析任务并行性和冲突                                     │
+│                                                                   │
+│  5. 完成条件                                                       │
+│     → 所有任务完成 → 所有 Agent shutdown                           │
+│     → 更新 orchestration_status.json                               │
+│                                                                   │
+└──────────────────────────────────────────────────────────────────┘
+
+Task Assignment Strategy:
+┌─────────────────────────────────────────────────────────────────┐
+│ 1. 解析 TASKS.md 获取当前阶段任务                                 │
+│    → node {SCRIPT:parse_tasks} next TASKS.md                     │
+│                                                                  │
+│ 2. 检测文件冲突                                                   │
+│    → {SCRIPT:detect_conflicts} < tasks.json                      │
+│                                                                  │
+│ 3. 分配策略                                                       │
+│    → 有冲突: 冲突任务分配给同一 Agent                             │
+│    → 无冲突: Round-robin 分配给各 Agent                           │
+│                                                                  │
+│ 4. 输出分配计划                                                   │
+│    {                                                             │
+│      "assignments": [                                            │
+│        {"agent": "dev-1", "tasks": ["T001", "T002"]},            │
+│        {"agent": "dev-2", "tasks": ["T003"]},                    │
+│        {"agent": "dev-3", "tasks": ["T004"]}                     │
+│      ],                                                          │
+│      "hasConflicts": false                                       │
+│    }                                                             │
+└─────────────────────────────────────────────────────────────────┘
+
+Conflict Resolution:
+┌─────────────────────────────────────────────────────────────────┐
+│ 文件冲突检测示例:                                                 │
+│                                                                  │
+│ Input:                                                           │
+│   T001 [P] 修改 src/user.ts                                      │
+│   T002 [P] 修改 src/user.ts                                      │
+│   T003 [P] 修改 src/order.ts                                     │
+│                                                                  │
+│ Output:                                                          │
+│   {                                                              │
+│     "hasConflicts": true,                                        │
+│     "conflicts": [                                               │
+│       {"file": "src/user.ts", "tasks": ["T001", "T002"]}         │
+│     ],                                                           │
+│     "safeGroups": [{"tasks": ["T003"]}]                          │
+│   }                                                              │
+│                                                                  │
+│ Assignment:                                                      │
+│   dev-1: T001, T002 (串行，因为冲突)                              │
+│   dev-2: T003 (独立)                                             │
+└─────────────────────────────────────────────────────────────────┘
+```
+
 **Manual 模式循环** (--manual):
 ```
 For each remaining task (顺序严格遵循 TASKS.md):
@@ -281,10 +374,11 @@ Note: Stop Hook (.claude/hooks/ralph-stop-hook.sh) 会在 Autonomous 模式下:
 ## 运行提示
 - **默认 Autonomous 模式**: 遇错自动重试，无需人工干预
 - **使用 `--manual` 退出**: 适合需要人工判断的复杂场景
+- **使用 `--team` 并行**: 适合大量可并行任务的需求 [NEW: v4.7]
 - **使用 `/cancel-ralph` 停止**: 紧急停止 Autonomous 循环
 - 始终使用 quickstart 中提供的命令（测试、lint、db migrate 等）
 - Phase 2 的所有测试必须在实现前失败；若某测试直接通过，回滚并修正
-- 遵循 TASKS.md 标注的 `[P]` 仅表示逻辑上可并行，实际执行依旧串行
+- 遵循 TASKS.md 标注的 `[P]` 表示可并行，Team 模式下会真正并行执行
 - 如需恢复，可使用 `/flow-dev --task TXYZ` 指向首个未完成任务
 
 ## 错误处理
@@ -301,6 +395,13 @@ Note: Stop Hook (.claude/hooks/ralph-stop-hook.sh) 会在 Autonomous 模式下:
 - 达到 max_iterations → 输出状态报告（已完成/剩余任务），保持 development_in_progress
 - 紧急停止 → 使用 `/cancel-ralph` 删除状态文件，立即终止循环
 
+**Team 模式** [NEW: v4.7]:
+- 缺少资产 → 同 Manual 模式（Entry Gate 阻止）
+- 文件冲突 → 自动检测并分配给同一 Agent 串行执行
+- Agent 任务失败 → TeammateIdle Hook 触发重试
+- 所有 Agent 空闲但任务未完成 → 重新分配任务
+- 紧急停止 → 清理 Team 状态，所有 Agent shutdown
+
 ## 取消 Autonomous 循环
 
 ```bash

package/.claude/commands/flow/init.md

@@ -0,0 +1,45 @@
+---
+name: flow-init
+description: 'Initialize requirement structure. Usage: /flow-init "REQ-123|Title|URLs"'
+skill: workflow/flow-init
+---
+
+# Flow-Init Command (Trigger Entry)
+
+> 此文件为触发入口，详细实现见 `.claude/skills/workflow/flow-init/SKILL.md`
+
+## Usage
+
+```bash
+/flow-init "REQ-123|User Authentication"
+/flow-init "REQ-124|数据导出|https://docs.example.com/export-spec.md"
+/flow-init --interactive
+```
+
+## Quick Reference
+
+| Stage | Purpose | Output |
+|-------|---------|--------|
+| 1 | Entry Gate | 参数验证 |
+| 1.2 | Git Branch | feature/REQ-xxx-title |
+| 1.5 | Context Loading | ROADMAP/ARCHITECTURE |
+| 2 | Directory Init | 目录结构 |
+| 2.3 | Brainstorming | BRAINSTORM.md |
+| 2.5 | Research | research/* |
+| 3 | README | README.md |
+| 4 | Exit Gate | 5-Level 验证 |
+
+## Skill Location
+
+**Full Implementation**: `.claude/skills/workflow/flow-init/SKILL.md`
+
+**Resources**:
+- Scripts: `.claude/skills/workflow/flow-init/scripts/`
+- References: `.claude/skills/workflow/flow-init/references/`
+- Assets: `.claude/skills/workflow/flow-init/assets/`
+
+## Next Step
+
+```
+/flow-prd "${REQ_ID}"
+```

package/.claude/commands/flow/new.md

@@ -0,0 +1,279 @@
+---
+name: flow-new
+description: 'One-shot requirement flow. Usage: /flow-new "REQ-123|支持用户下单|https://plan.example.com/Q1"'
+templates:
+  orchestration: .claude/docs/templates/NEW_ORCHESTRATION_TEMPLATE.md
+guides:
+  troubleshoot: .claude/docs/guides/NEW_TROUBLESHOOTING.md
+---
+
+<!-- ============================================================
+     头文件引用语法规范 (Header File Reference Syntax)
+     ============================================================
+
+命令头文件格式:
+```yaml
+templates:
+  orchestration: .claude/docs/templates/NEW_ORCHESTRATION_TEMPLATE.md
+guides:
+  troubleshoot: .claude/docs/guides/NEW_TROUBLESHOOTING.md
+```
+
+引用语法:
+- {TEMPLATE:orchestration} → 加载 .claude/docs/templates/NEW_ORCHESTRATION_TEMPLATE.md
+- {GUIDE:troubleshoot}     → 参考 .claude/docs/guides/NEW_TROUBLESHOOTING.md
+
+规则: 遇到 {TYPE:key} 占位符时，去头文件 YAML 中找对应类型的 key，获取文件路径并加载。
+============================================================ -->
+
+# Flow-New - 一键需求开发流
+
+## User Input
+```text
+$ARGUMENTS = "REQ_ID|TITLE|PLAN_URLS?"
+```
+
+**格式**:
+- REQ_ID: 需求编号 (例如: REQ-123)
+- TITLE: 需求标题
+- PLAN_URLS: 计划文档 URL，多个用逗号分隔 (可选)
+
+**示例**:
+```
+/flow-new "REQ-123|支持用户下单|https://plan.example.com/Q1"
+/flow-new "REQ-124|用户权限管理"
+```
+
+---
+
+## 执行前加载
+
+**详细编排流程**:
+→ 参见 `{TEMPLATE:orchestration}` 获取完整编排逻辑
+
+**故障排查**:
+→ 遇到问题参考 `{GUIDE:troubleshoot}`
+
+---
+
+## 架构说明
+
+**设计理念**: `flow-new` 是编排器（Orchestrator），串行调用当前主干命令，避免人工串接阶段。
+
+**调用链** (v4.1):
+```
+/flow-new "REQ-123|Title|URLs"
+  ↓
+[1/6] /flow-init "REQ-123|Title|URLs"
+      → 创建需求目录 + research + BRAINSTORM
+  ↓
+[2/6] /flow-clarify "REQ-123" (可选)
+      → 仅在需求存在歧义时触发
+  ↓
+[3/6] /flow-spec "REQ-123"
+      → PRD → Tech+UI(并行) → Epic/TASKS
+  ↓
+[4/6] /flow-dev "REQ-123"
+      → TDD 执行 (测试先失败，再实现)
+  ↓
+[5/6] /flow-quality "REQ-123" --full
+      → 规格合规 + 代码质量 + 安全验证
+  ↓
+[6/6] /flow-release "REQ-123"
+      → 发布计划 + PR 创建 + 分支收尾
+```
+
+---
+
+## 执行流程骨架
+
+### [1/6] 初始化 → /flow-init
+
+```
+调用: /flow-init "${REQ_ID}|${TITLE}|${PLAN_URLS}"
+检查: orchestration_status.json.status === "initialized"
+→ 详见 {TEMPLATE:orchestration} Stage 1
+```
+
+**输出**:
+- Git 分支: `feature/${REQ_ID}-${slug(BRANCH_TITLE_EN)}`
+- 需求目录与 research 上下文
+- `BRAINSTORM.md`
+
+---
+
+### [2/6] 需求澄清（可选）→ /flow-clarify
+
+```
+触发条件: 需求存在歧义、边界不清、验收标准冲突
+调用: /flow-clarify "${REQ_ID}"
+→ 详见 .claude/commands/flow/clarify.md
+```
+
+**输出**:
+- `clarifications/*.md` (如触发)
+
+---
+
+### [3/6] 统一规格阶段 → /flow-spec
+
+```
+调用: /flow-spec "${REQ_ID}" [--skip-tech] [--skip-ui]
+默认: PRD + Tech + UI + Epic/TASKS
+→ 详见 .claude/commands/flow/spec.md
+```
+
+**输出**:
+- `PRD.md`
+- `TECH_DESIGN.md` / `UI_PROTOTYPE.html` (按模式)
+- `EPIC.md` + `TASKS.md`
+
+---
+
+### [4/6] 开发执行 → /flow-dev
+
+```
+调用: /flow-dev "${REQ_ID}"
+执行模式: TDD
+  1) 先写测试并确认失败
+  2) 再实现功能
+  3) 最终测试通过
+→ 详见 .claude/commands/flow/dev.md
+```
+
+**输出**:
+- 实现代码 + 测试代码
+- `TASKS.md` 勾选状态更新
+
+---
+
+### [5/6] 质量验证 → /flow-quality
+
+```
+调用: /flow-quality "${REQ_ID}" --full
+检查: 规格一致性、代码质量、安全与测试门禁
+→ 详见 .claude/commands/flow/quality.md
+```
+
+**输出**:
+- `SPEC_REVIEW.md`
+- `CODE_QUALITY_REVIEW.md`
+- `SECURITY_REPORT.md`
+
+---
+
+### [6/6] 发布管理 → /flow-release
+
+```
+调用: /flow-release "${REQ_ID}"
+执行: 生成 RELEASE_PLAN、创建 PR、执行收尾策略
+→ 详见 .claude/commands/flow/release.md
+```
+
+**输出**:
+- `RELEASE_PLAN.md`
+- Pull Request / 合并策略决策
+
+---
+
+## 进度展示
+
+**实时进度**:
+
+```
+🎯 CC-DevFlow 完整需求开发流程 (v4.1)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+需求: REQ-123 | 支持用户下单
+
+[1/6] ✅ 初始化完成
+[2/6] ✅ 澄清完成 (可选)
+[3/6] ✅ 统一规格完成
+[4/6] 🔄 开发执行中... (8/18 已完成)
+[5/6] ⏳ 等待质量验证...
+[6/6] ⏳ 等待发布管理...
+```
+
+---
+
+## 输出产物
+
+```
+devflow/requirements/${REQ_ID}/
+├── BRAINSTORM.md
+├── research/
+├── PRD.md
+├── TECH_DESIGN.md                  # 若未跳过 tech
+├── UI_PROTOTYPE.html               # 若未跳过 ui 且识别到 UI 需求
+├── EPIC.md
+├── TASKS.md
+├── SPEC_REVIEW.md                  # flow-quality --full
+├── CODE_QUALITY_REVIEW.md          # flow-quality --full
+├── SECURITY_REPORT.md              # flow-quality --full
+└── RELEASE_PLAN.md
+```
+
+---
+
+## 中断与恢复
+
+```bash
+# 查看当前状态
+/flow-status REQ-123
+
+# 从中断点恢复
+/flow-restart "REQ-123"
+
+# 手动执行后续阶段
+/flow-spec "REQ-123"
+/flow-dev "REQ-123" --resume
+/flow-quality "REQ-123" --full
+```
+
+---
+
+## 使用建议
+
+### ✅ 适合使用 flow-new
+
+- 明确需求，需要一口气走完整条流水线
+- 团队希望减少阶段切换的上下文开销
+- 希望快速拿到可评审发布结果
+
+### ❌ 建议使用阶段化命令
+
+- 需求高度不确定，需频繁往返讨论
+- 规格阶段需要多人异步审阅
+- 开发阶段需要多次暂停/切换优先级
+
+---
+
+## Next Step
+
+```bash
+# 查看 PR 状态
+cat devflow/requirements/${REQ_ID}/RELEASE_PLAN.md | grep "PR URL"
+
+# 审查 PR
+gh pr view <PR_NUMBER>
+
+# 合并 PR
+gh pr merge <PR_NUMBER>
+```
+
+---
+
+**Related Documentation**:
+- [NEW_ORCHESTRATION_TEMPLATE.md](../../docs/templates/NEW_ORCHESTRATION_TEMPLATE.md) - 详细编排流程
+- [NEW_TROUBLESHOOTING.md](../../docs/guides/NEW_TROUBLESHOOTING.md) - 故障排查指南
+- [flow-init.md](./init.md) - 初始化阶段
+- [flow-clarify.md](./clarify.md) - 需求澄清阶段
+- [flow-spec.md](./spec.md) - 统一规格阶段
+- [flow-dev.md](./dev.md) - 开发阶段 (TDD)
+- [flow-quality.md](./quality.md) - 统一质量验证阶段
+- [flow-release.md](./release.md) - 发布阶段
+- [flow-fix.md](./fix.md) - Bug 修复流程
+
+---
+
+**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/commands/flow/quality.md

@@ -0,0 +1,159 @@
+---
+name: flow-quality
+description: Combined quality verification (replaces flow-review + flow-qa)
+version: 3.0.0
+---
+
+# /flow-quality
+
+> **[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md
+
+## Purpose
+
+Combined quality verification command that replaces the separate `/flow-review` and `/flow-qa` commands.
+Provides both quick programmatic verification and full comprehensive review.
+
+## Usage
+
+```bash
+# Quick mode (default) - programmatic verification only
+/flow-quality [REQ-ID]
+
+# Full mode - comprehensive review including spec compliance
+/flow-quality [REQ-ID] --full
+```
+
+## Modes
+
+### Quick Mode (Default)
+
+Fast programmatic verification using quality-gates.yml:
+
+1. **Lint Check** - `npm run lint`
+2. **Type Check** - `npm run typecheck`
+3. **Unit Tests** - `npm test`
+
+**Use Case**: Rapid iteration during development, CI/CD pipelines.
+
+**Duration**: ~1-2 minutes
+
+### Full Mode (`--full`)
+
+Comprehensive review including:
+
+1. **Programmatic Checks** (same as quick mode)
+2. **Spec Compliance Review** - Verify implementation matches PRD/TECH_DESIGN
+3. **Code Quality Review** - Structure, patterns, Constitution compliance
+4. **Security Scan** - `npm audit`, secret detection
+5. **Integration Tests** - `npm run test:integration` (if available)
+
+**Use Case**: Before PR creation, milestone completion.
+
+**Duration**: ~5-10 minutes
+
+## Entry Gate
+
+```yaml
+prerequisites:
+  - development_complete: true
+  - TASKS.md: All tasks marked [x]
+  - Tests: All passing
+```
+
+## Exit Gate
+
+### Quick Mode
+```yaml
+exit_criteria:
+  - lint: pass
+  - typecheck: pass
+  - tests: pass
+```
+
+### Full Mode
+```yaml
+exit_criteria:
+  - lint: pass
+  - typecheck: pass
+  - tests: pass
+  - spec_review: PASS
+  - code_quality: PASS
+  - security: no high-severity issues
+```
+
+## Output
+
+### Quick Mode
+```
+✅ Quality Gate PASSED (Quick Mode)
+
+  ✓ Lint Check
+  ✓ Type Check
+  ✓ Unit Tests (42 passed)
+
+Duration: 1m 23s
+```
+
+### Full Mode
+```
+✅ Quality Gate PASSED (Full Mode)
+
+Programmatic Checks:
+  ✓ Lint Check
+  ✓ Type Check
+  ✓ Unit Tests (42 passed)
+  ✓ Integration Tests (8 passed)
+
+Reviews:
+  ✓ Spec Compliance: PASS
+  ✓ Code Quality: PASS
+  ✓ Security: No issues
+
+Reports Generated:
+  - SPEC_REVIEW.md
+  - CODE_QUALITY_REVIEW.md
+  - SECURITY_REPORT.md
+
+Duration: 7m 45s
+```
+
+## Integration
+
+### With flow-dev
+
+After `/flow-dev` completes, the orchestrator recommends:
+```
+status: "development_complete"
+  → Recommend: /flow-quality (quick verification)
+  → Alternative: /flow-quality --full (comprehensive review)
+```
+
+### With flow-release
+
+`/flow-release` requires quality gate to pass:
+```yaml
+flow-release:
+  prerequisites:
+    - quality_complete: true
+```
+
+## Deprecation Notice
+
+The following commands are deprecated in v3.0:
+
+- `/flow-review` → Use `/flow-quality --full`
+- `/flow-qa` → Use `/flow-quality --full`
+
+These commands still work for backward compatibility but will show a deprecation warning.
+
+## Scripts
+
+- `.claude/scripts/flow-quality-quick.sh` - Quick verification
+- `.claude/scripts/flow-quality-full.sh` - Full verification
+- `.claude/scripts/run-quality-gates.sh` - Core gate execution
+
+## Related
+
+- **Config**: `.claude/config/quality-gates.yml`
+- **Error Log**: `ERROR_LOG.md` (errors recorded here)
+- **Orchestrator**: Updates `orchestration_status.json` on completion