cc-devflow 4.1.5 → 4.1.6

package/.claude/commands/flow/spec.md

@@ -1,186 +1,36 @@
 ---
 name: flow-spec
-description: 'Unified specification phase: PRD → Tech+UI (parallel) → Epic/Tasks. Usage: /flow-spec "REQ-123" [--skip-tech] [--skip-ui]'
-scripts:
-  prereq: .claude/scripts/check-prerequisites.sh
-  validate_research: .claude/scripts/validate-research.sh
-  validate_constitution: .claude/scripts/validate-constitution.sh
+description: 'Generate task-manifest from requirement context. Usage: /flow:spec "REQ-123" [--overwrite]'
+skill: workflow/flow-spec
 ---
 
-# Flow-Spec - 统一规格阶段命令
+# Flow-Spec Command (Harness Planning)
 
-> **v4.1 新增**: 合并 flow-prd/flow-tech/flow-ui/flow-epic 为单一命令
+> 触发入口：执行细节由 `.claude/skills/workflow/flow-spec/SKILL.md` 定义。
 
 ## User Input
 
 ```text
-$ARGUMENTS = "REQ_ID [--skip-tech] [--skip-ui]"
+$ARGUMENTS = "REQ_ID [--overwrite]"
 ```
 
-若未提供 REQ_ID 则根据当前分支或 `DEVFLOW_REQ_ID` 自动解析。
-
-## 命令格式
+## Usage
 
 ```bash
-# Full Mode (默认) - PRD + Tech + UI + Epic
-/flow-spec "REQ-123"
-
-# Quick Mode (小需求) - PRD + Epic only
-/flow-spec "REQ-123" --skip-tech --skip-ui
-
-# Backend Only - PRD + Tech + Epic
-/flow-spec "REQ-123" --skip-ui
-
-# Frontend Only - PRD + UI + Epic
-/flow-spec "REQ-123" --skip-tech
-```
-
-## Mode Matrix
-
-| Mode | Flags | Agents | Output |
-|------|-------|--------|--------|
-| Full | (default) | PRD + Tech + UI + Epic | PRD.md, TECH_DESIGN.md, UI_PROTOTYPE.html, EPIC.md, TASKS.md |
-| Quick | `--skip-tech --skip-ui` | PRD + Epic | PRD.md, EPIC.md, TASKS.md |
-| Backend | `--skip-ui` | PRD + Tech + Epic | PRD.md, TECH_DESIGN.md, EPIC.md, TASKS.md |
-| Frontend | `--skip-tech` | PRD + UI + Epic | PRD.md, UI_PROTOTYPE.html, EPIC.md, TASKS.md |
-
-## 执行流程
-
-**加载 Skill 指令**:
-```
-→ 读取 .claude/skills/workflow/flow-spec/SKILL.md
-→ 按 SKILL.md 中定义的 Execution Flow 执行
-```
-
-### 阶段 1: Entry Gate
-
-```yaml
-Prerequisites:
-  1. REQ_ID 解析:
-     - 从参数获取
-     - 或从当前分支推断 (feature/REQ-XXX-*)
-     - 或从 orchestration_status.json 获取
-
-  2. BRAINSTORM.md 存在:
-     - 路径: devflow/requirements/${REQ_ID}/BRAINSTORM.md
-     - 必须包含: 需求描述、目标用户、核心功能
-
-  3. Research 完成:
-     - 路径: devflow/requirements/${REQ_ID}/research/research.md
-     - 无 TODO/PLACEHOLDER
-
-  4. Status Check:
-     - orchestration_status.status ∈ {"initialized", "spec_failed"}
-
-  5. Constitution Gate:
-     - 读取 BRAINSTORM.md 验证需求边界
-```
-
-### 阶段 2: PRD Generation (Sequential)
-
-```yaml
-Agent: prd-writer (research-type)
-Input:
-  - BRAINSTORM.md
-  - research/research.md
-  - research/internal/codebase-overview.md
-
-Output:
-  - PRD.md
-
-Rules:
-  - ANTI-EXPANSION: 未提及 → [NEEDS CLARIFICATION]
-  - NO TECH DETAILS: 只关注 WHAT/WHY
-  - STORY INDEPENDENCE: 每个故事有独立测试
-```
-
-### 阶段 3: Tech + UI (Parallel)
-
-```yaml
-Parallel Execution:
-  tech-architect (if !--skip-tech):
-    Input: PRD.md, research/codebase-overview.md
-    Output: TECH_DESIGN.md, data-model.md, contracts/
-
-  ui-designer (if !--skip-ui AND UI detected):
-    Input: PRD.md, STYLE.md (optional)
-    Output: UI_PROTOTYPE.html, ui_design_strategy.md
-
-Method:
-  - 使用 Task tool 并行调用两个 agent
-  - 等待两者完成后进入 Stage 4
+/flow:spec "REQ-123"
+/flow:spec "REQ-123" --overwrite
 ```
 
-### 阶段 4: Epic Generation (Sequential)
+## Internal Execution
 
-```yaml
-Agent: planner (research-type)
-Input:
-  - PRD.md
-  - TECH_DESIGN.md (if exists)
-  - UI_PROTOTYPE.html (if exists)
+- `npm run harness:plan -- --change-id <REQ_ID> [--overwrite]`
 
-Output:
-  - EPIC.md
-  - TASKS.md
+## Output
 
-Rules:
-  - TDD Order: Phase 2 (Tests) → Phase 3 (Implementation)
-  - Bite-Sized Tasks: 每个 step 2-5 分钟
-  - Phase -1 Gates: Simplicity, Anti-Abstraction, Integration-First
-```
-
-### 阶段 5: Exit Gate
-
-```yaml
-File Checks:
-  - [ ] PRD.md exists, no {{PLACEHOLDER}}
-  - [ ] TECH_DESIGN.md exists (if !--skip-tech)
-  - [ ] UI_PROTOTYPE.html exists (if !--skip-ui AND UI detected)
-  - [ ] EPIC.md exists, no {{PLACEHOLDER}}
-  - [ ] TASKS.md exists, TDD order correct
-
-Status Update:
-  - orchestration_status.status = "spec_complete"
-  - orchestration_status.phase = "spec"
-```
+- `devflow/requirements/<REQ_ID>/task-manifest.json`
 
-## 输出
-
-```
-devflow/requirements/${REQ_ID}/
-├── PRD.md                          # Always
-├── TECH_DESIGN.md                  # If !--skip-tech
-├── data-model.md                   # If !--skip-tech
-├── contracts/openapi.yaml          # If !--skip-tech
-├── UI_PROTOTYPE.html               # If !--skip-ui AND UI detected
-├── EPIC.md                         # Always
-├── TASKS.md                        # Always
-└── orchestration_status.json       # Updated
-```
-
-## 错误处理
-
-- **Entry Gate 失败**: 返回具体缺失项，指导用户运行 `/flow-init`
-- **PRD 生成失败**: status = "spec_failed"，可重试
-- **Tech/UI 失败**: 继续执行，标记为 skipped
-- **Epic 失败**: status = "spec_failed"，可用 `--from=epic` 重试
-
-## 下一步
+## Next Step
 
 ```bash
-/flow-dev "${REQ_ID}"
+/flow:dev "<REQ_ID>"
 ```
-
-## Agent References
-
-| Agent | Purpose | Location |
-|-------|---------|----------|
-| prd-writer | PRD 生成 | `.claude/agents/prd-writer.md` |
-| tech-architect | 技术设计 | `.claude/agents/tech-architect.md` |
-| ui-designer | UI 原型 | `.claude/agents/ui-designer.md` |
-| planner | Epic/Tasks | `.claude/agents/planner.md` |
-
-## 详细指令
-
-完整执行逻辑见: `.claude/skills/workflow/flow-spec/SKILL.md`

package/.claude/commands/flow/status.md

@@ -1,6 +1,6 @@
 ---
 name: flow-status
-description: 'Query development progress status for cc-devflow requirements. Usage: /flow-status [REQ-ID]'
+description: 'Query development progress status for cc-devflow requirements. Usage: /flow:status [REQ-ID]'
 scripts:
   prereq: .claude/scripts/check-prerequisites.sh
   generate_status: .claude/scripts/generate-status-report.sh
@@ -28,9 +28,9 @@ $ARGUMENTS = "[REQ_ID?] [--all] [--bugs] [--detailed] [--summary]"
    → devflow/bugs/*/orchestration_status.json
 3. 读取每个状态文件及 EXECUTION_LOG.md 头部，提取:
    → status, phase, completedSteps, phase0/phase1 flag, lastUpdated
-   → 是否存在 PRD/TECH_DESIGN/data-model/contracts/quickstart/EPIC/TASKS/QA 报告
+   → 是否存在 context-package/task-manifest/report-card/RELEASE_NOTE
 4. 若 `--branches`: 读取 git 分支与 upstream 状态
-5. 若 `--detailed`: 关联 PRD/EPIC/TASKS 进度、QA/Release 结论
+5. 若 `--detailed`: 关联 task-manifest 任务统计、report-card 结论、release note
 ```
 
 ### 3. 输出格式
@@ -39,12 +39,12 @@ $ARGUMENTS = "[REQ_ID?] [--all] [--bugs] [--detailed] [--summary]"
 - **Summary/All**: 使用 {SCRIPT:generate_status} 生成聚合报告。
 
 ### 4. 建议动作
-- 根据状态字段提示下一命令：
-  - `status=initialized` → `/flow-prd`
-  - `phase0_complete=false` → `/flow-init` consolidate
-  - `phase1_complete=false` → `/flow-tech`
-  - `status=epic_complete` → `/flow-dev`
-  - `status=quality_complete`（兼容 `qa_complete`）→ `/flow-release`
+  - 根据状态字段提示下一命令（优先主链）：
+    - `status=initialized` 或 `status=context_packed` → `/flow:spec`
+    - `status=planned` 或 `status=spec_complete` → `/flow:dev`
+    - `status=development_in_progress` 且有失败任务 → `/flow:dev --resume`
+    - `status=development_complete` → `/flow:verify --strict`
+    - `status=quality_complete` 或 `status=verified` → `/flow:release`
 
 ## 输出样例
 ```
@@ -52,9 +52,9 @@ $ARGUMENTS = "[REQ_ID?] [--all] [--bugs] [--detailed] [--summary]"
 ┌─────────┬──────────────┬───────────────┬────────────┬──────────┐
 │ ID      │ Title        │ Status        │ Phase      │ Next     │
 ├─────────┼──────────────┼───────────────┼────────────┼──────────┤
-│ REQ-123 │ 下单流程优化   │ epic_complete │ planning   │ /flow-dev │
-│ REQ-124 │ 权限矩阵       │ quality_complete │ release │ /flow-release │
-│ REQ-125 │ 账单导出       │ prd_complete  │ technical  │ /flow-tech │
+│ REQ-123 │ 下单流程优化   │ planned        │ planning   │ /flow:dev │
+│ REQ-124 │ 权限矩阵       │ quality_complete │ verify  │ /flow:release │
+│ REQ-125 │ 账单导出       │ initialized    │ init       │ /flow:spec │
 └─────────┴──────────────┴───────────────┴────────────┴──────────┘
 ```
 

package/.claude/commands/flow/update.md

@@ -1,6 +1,6 @@
 ---
 name: flow-update
-description: 'Update task progress for cc-devflow requirements. Usage: /flow-update "REQ-123" "T012" [OPTIONS]'
+description: 'Update task progress for cc-devflow requirements. Usage: /flow:update "REQ-123" "T012" [OPTIONS]'
 scripts:
   prereq: .claude/scripts/check-prerequisites.sh
   check_tasks: .claude/scripts/check-task-status.sh
@@ -17,7 +17,7 @@ $ARGUMENTS = "REQ_ID TASK_ID [--status=STATE] [--progress=PCT] [--estimate=HRS]
 
 ## 命令格式
 ```text
-/flow-update "REQ_ID" "TASK_ID" [OPTIONS]
+/flow:update "REQ_ID" "TASK_ID" [OPTIONS]
 ```
 
 ### 支持选项
@@ -106,6 +106,6 @@ $ARGUMENTS = "REQ_ID TASK_ID [--status=STATE] [--progress=PCT] [--estimate=HRS]
 ```
 
 ## 下一步
-- 若所有任务完成：立即运行 `/flow-quality`（需要深度审查时再加 `--full`）。
+- 若所有任务完成：立即运行 `/flow:verify --strict`。
 - 若任务被阻塞：添加 `blocked` 注释并通知相关负责人。
-- 周期性执行 `/flow-status` 获取进度总览。
+- 周期性执行 `/flow:status` 获取进度总览。

package/.claude/commands/flow/upgrade.md

@@ -1,6 +1,6 @@
 ---
 name: flow-upgrade
-description: 'PRD version management, analysis, and application workflow. Usage: /flow-upgrade "REQ-123" --analyze or --version="2.0.0" --reason="..."'
+description: 'PRD version management, analysis, and application workflow. Usage: /flow:upgrade "REQ-123" --analyze or --version="2.0.0" --reason="..."'
 scripts:
   prereq: .claude/scripts/check-prerequisites.sh
   manage_constitution: .claude/scripts/manage-constitution.sh
@@ -34,7 +34,7 @@ $ARGUMENTS = "REQ_ID [--analyze] [--version=SEMVER] [--reason='...'] [--rollback
    → Git 工作区需干净（除非只做 analyze）。
 
 3. 状态确认
-   → orchestration_status.status 至少为 "prd_complete"。
+   → orchestration_status.status 至少为 "initialized"。
    → 若后续流程在开发阶段进行，提示可能影响当前迭代。
 ```
 
@@ -70,7 +70,7 @@ $ARGUMENTS = "REQ_ID [--analyze] [--version=SEMVER] [--reason='...'] [--rollback
    → EXECUTION_LOG.md 记录升级摘要。
 
 5. 触发后续动作
-   → 提示重新运行 /flow-tech、/flow-epic 等受影响阶段。
+   → 提示重新运行 `/flow:spec`、`/flow:dev`、`/flow:verify` 等受影响阶段。
 ```
 
 ### 阶段 2C: 回滚 (--rollback)
@@ -91,7 +91,7 @@ $ARGUMENTS = "REQ_ID [--analyze] [--version=SEMVER] [--reason='...'] [--rollback
 ### 阶段 3: Exit Gate
 ```
 1. 核验版本快照目录、CHANGELOG、影响报告是否生成。
-2. 若版本号更新成功，提示下一步（重新跑 /flow-tech /flow-epic）。
+2. 若版本号更新成功，提示下一步（重新跑 `/flow:spec` / `/flow:dev` / `/flow:verify`）。
 3. 失败时保持原状态，给出恢复指引。
 ```
 
@@ -111,5 +111,5 @@ $ARGUMENTS = "REQ_ID [--analyze] [--version=SEMVER] [--reason='...'] [--rollback
 
 ## 下一步
 - 若版本包含重大变更：立即通知团队重新生成技术方案和规划。
-- 使用 `/flow-status` 检查其他需求是否依赖该版本。
-- 需要宪法变更时调用 `/flow-constitution --amend`。
+- 使用 `/flow:status` 检查其他需求是否依赖该版本。
+- 需要宪法变更时调用 `/flow:constitution --amend`。

package/.claude/commands/flow/verify.md

@@ -1,96 +1,37 @@
 ---
 name: flow-verify
-description: 'Comprehensive consistency verification across documents and implementation. Usage: /flow-verify "REQ-123" or /flow-verify --all'
-scripts:
-  prereq: .claude/scripts/check-prerequisites.sh
-  validate_constitution: .claude/scripts/validate-constitution.sh
-  generate_status: .claude/scripts/generate-status-report.sh
+description: 'Run layered quality gates and produce report-card. Usage: /flow:verify "REQ-123" [--strict] [--skip-review]'
+skill: workflow/flow-verify
 ---
 
-# Flow-Verify - 一致性验证命令
+# Flow-Verify Command (Harness Gates)
+
+> 触发入口：执行细节由 `.claude/skills/workflow/flow-verify/SKILL.md` 定义。
 
 ## User Input
+
 ```text
-$ARGUMENTS = "REQ_ID? [--all] [--summary] [--critical-only] [--since=ISO] [--diff=RANGE] [--documents-only|--implementation-only|--tests-only]"
+$ARGUMENTS = "REQ_ID [--strict] [--skip-review]"
 ```
-缺省 REQ_ID 时使用当前分支；`--all` 针对所有需求。
-
-## 验证维度
-- 文档链路：`PRD.md → TECH_DESIGN.md → data-model.md → contracts/ → EPIC.md → TASKS.md`
-- 实现链路：`代码实现 ↔ tests ↔ quickstart.md`
-- 状态链路：`orchestration_status.json`、`EXECUTION_LOG.md`
 
-## 执行流程
+## Usage
 
-### 阶段 1: Entry Gate
+```bash
+/flow:verify "REQ-123"
+/flow:verify "REQ-123" --strict
+/flow:verify "REQ-123" --strict --skip-review
 ```
-1. 参数解析
-   → 支持单需求、批量 (--all)、增量 (--since/--diff)、维度过滤 (--documents-only 等)
 
-2. 前置检查
-   → {SCRIPT:prereq} --json
-   → 确保存在: PRD.md, TECH_DESIGN.md, data-model.md, contracts/, quickstart.md, EPIC.md, TASKS.md
-   → orchestration_status.status 至少为 "dev_complete"（或用户指定跳过实现验证）
+## Internal Execution
 
-3. 选择验证集合
-   → 单需求: 使用传入 ID
-   → --all: 枚举 devflow/requirements/**
-```
+- `npm run harness:verify -- --change-id <REQ_ID> [--strict] [--skip-review]`
 
-### 阶段 2: 验证准备
-```
-1. 汇总上下文
-   → 读取研究/设计/规划/实现资产，构建追溯矩阵
-2. 配置验证级别
-   → 默认: 全量
-   → --summary: 仅关键阻断项
-   → --critical-only: 只输出严重问题
-3. 更新 EXECUTION_LOG.md 记录验证开始
-```
-
-### 阶段 3: Consistency Checks
-```
-1. 文档一致性
-   → PRD 用户故事 ↔ EPIC scopes ↔ TASKS phases
-   → TECH_DESIGN 决策 ↔ data-model / contracts / quickstart
+## Output
 
-2. 实现一致性
-   → TASKS 任务 ↔ Git 提交 ↔ 测试文件
-   → quickstart 命令可执行性（dry-run 或脚本验证）
+- `devflow/requirements/<REQ_ID>/report-card.json`
 
-3. 质量守则
-   → {SCRIPT:validate_constitution} --type verify --severity warning
-   → 检查 Simplicity / Anti-Abstraction / Integration-First、No Partial Implementation、No Dead Code 等
-```
+## Next Step
 
-### 阶段 4: 报告输出
+```bash
+/flow:release "<REQ_ID>"
 ```
-1. 生成 report
-   → 路径: devflow/requirements/${REQ_ID}/VERIFY_REPORT.md
-   → 包含: 概览、通过/失败项、严重度、建议、受影响文件
-
-2. 更新状态
-   → orchestration_status:
-        lastVerificationAt = ISO timestamp
-        verificationStatus = "passed" 或 "issues_found"
-   → EXECUTION_LOG 记录完成
-
-3. 可选: {SCRIPT:generate_status} 汇总全部需求验证结果
-```
-
-## 输出
-```
-✅ VERIFY_REPORT.md
-✅ orchestration_status.json（记录验证状态）
-✅ EXECUTION_LOG.md 更新
-```
-
-## 错误处理
-- 缺失关键资产 → 提示前置命令（/flow-prd、/flow-tech、/flow-epic、/flow-dev）。
-- 验证脚本失败 → 输出日志位置，保持 verificationStatus = "failed".
-- Constitution 违规 → 报告标记为 BLOCKER，需在发版前修复。
-
-## 建议后续
-1. 对 issues_found 的需求，回到对应阶段修复。
-2. 在 `/flow-release` 前确保最新验证为 PASS。
-3. 将验证报告纳入 QA 签核材料。

package/.claude/commands/flow/workspace.md

@@ -126,7 +126,7 @@ devflow/workspace/
 
 ### With flow-init
 
-When `/flow-init` creates a new requirement (and workspace already initialized):
+When `/flow:init` creates a new requirement (and workspace already initialized):
 ```bash
 # Auto-update workspace
 echo "REQ-XXX" > devflow/workspace/{developer}/.current-req

package/.claude/docs/guides/INIT_TROUBLESHOOTING.md

@@ -1,6 +1,6 @@
 # Flow-Init Troubleshooting Guide
 
-> Quick reference for `/flow-init` errors and recovery
+> Quick reference for `/flow:init` errors and recovery
 
 ---
 
@@ -18,7 +18,7 @@
 ```bash
 ❌ ERROR: devflow/requirements/REQ-123/ already exists
 ```
-**Fix**: 使用不同 ID 或 `/flow-init "REQ-123|..." --force` 强制覆盖
+**Fix**: 使用不同 ID 或 `/flow:init "REQ-123|..." --force` 强制覆盖
 
 ---
 
@@ -53,7 +53,7 @@
 ```bash
 rm -rf devflow/requirements/REQ-123/
 git branch -D feature/REQ-123-*
-/flow-init "REQ-123|Title|URLs"
+/flow:init "REQ-123|Title|URLs"
 ```
 
 ### Recover from Interruption
@@ -69,7 +69,7 @@ jq '.phase0_complete = true' devflow/requirements/REQ-123/orchestration_status.j
 mv tmp.json devflow/requirements/REQ-123/orchestration_status.json
 
 # 继续下一阶段
-/flow-prd "REQ-123"
+/flow:spec "REQ-123"
 ```
 
 ### Rebuild Research.md from Tasks.json
@@ -95,8 +95,8 @@ bash .claude/scripts/validate-research.sh "$REQ_DIR"
 
 ### Command-Line Flags
 ```bash
-/flow-init "REQ-123|..." --force        # 强制覆盖现有需求
-/flow-init --interactive                # 交互式输入模式
+/flow:init "REQ-123|..." --force        # 强制覆盖现有需求
+/flow:init --interactive                # 交互式输入模式
 ```
 
 ---
@@ -104,7 +104,7 @@ bash .claude/scripts/validate-research.sh "$REQ_DIR"
 ## FAQ
 
 **Q: 如何跳过 MCP 研究阶段？**
-A: `SKIP_MCP_RESEARCH=1 /flow-init "REQ-123|..."`
+A: `SKIP_MCP_RESEARCH=1 /flow:init "REQ-123|..."`
 
 **Q: Context Loading 阶段找不到 ROADMAP.md 怎么办？**
 A: 可选步骤，不影响执行。如需路线图，先运行 `/core-roadmap`