cc-devflow 4.1.5 → 4.1.6

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

@@ -1,279 +1,23 @@
 ---
 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
+description: 'Deprecated. Use /flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release.'
 ---
 
-<!-- ============================================================
-     头文件引用语法规范 (Header File Reference Syntax)
-     ============================================================
+# /flow:new (Deprecated)
 
-命令头文件格式:
-```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:new` 已停止作为默认入口。
 
-```
-调用: /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
-```
-
----
-
-## 中断与恢复
+## Migration Path
 
 ```bash
-# 查看当前状态
-/flow-status REQ-123
-
-# 从中断点恢复
-/flow-restart "REQ-123"
-
-# 手动执行后续阶段
-/flow-spec "REQ-123"
-/flow-dev "REQ-123" --resume
-/flow-quality "REQ-123" --full
+/flow:init "REQ-123|Feature|URLs?"
+/flow:spec "REQ-123"
+/flow:dev "REQ-123"
+/flow:verify "REQ-123" --strict
+/flow:release "REQ-123"
 ```
 
----
-
-## 使用建议
-
-### ✅ 适合使用 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 修复流程
-
----
+## Why
 
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md
+- 旧一键编排耦合了已下线阶段（clarify/checklist/quality）。
+- 新主链将复杂度收敛到 harness 引擎，支持 checkpoint 恢复与分层门禁。

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

@@ -1,164 +1,21 @@
 ---
 name: flow-quality
-description: Combined quality verification (replaces flow-review + flow-qa)
-version: 3.0.0
+description: 'Deprecated. Use /flow:verify for quick/strict quality gates.'
 ---
 
-# /flow-quality
+# /flow:quality (Deprecated)
 
-> **[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md
+`/flow:quality` 已废弃。
 
-## 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
+## Migration
 
 ```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
+/flow:verify "REQ-123"
+/flow:verify "REQ-123" --strict
+/flow:verify "REQ-123" --strict --skip-review
 ```
-✅ Quality Gate PASSED (Quick Mode)
-
-  ✓ Lint Check
-  ✓ Type Check
-  ✓ Unit Tests (42 passed)
-
-Reports Generated (when REQ-ID resolved):
-  - TEST_REPORT.md
-  - SECURITY_REPORT.md
-
-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
-  - TEST_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
+## Reason
 
-- **Config**: `.claude/config/quality-gates.yml`
-- **Error Log**: `ERROR_LOG.md` (errors recorded here)
-- **Orchestrator**: Updates `orchestration_status.json` on completion
+- 质量验证统一收口到 harness verify。
+- 门禁结果统一输出到 `report-card.json` 并作为 `/flow:release` 唯一准入条件。

package/.claude/commands/flow/release.md

@@ -1,99 +1,36 @@
 ---
 name: flow-release
-description: 'Complete requirement and update progress. Usage: /flow-release "REQ-123" or /flow-release'
-scripts:
-  prereq: .claude/scripts/check-prerequisites.sh
-  check_tasks: .claude/scripts/check-task-status.sh
-  validate_constitution: .claude/scripts/validate-constitution.sh
-  generate_status: .claude/scripts/generate-status-report.sh
-  verify_gate: .claude/scripts/verify-gate.sh
-skills:
-  verification: .claude/skills/verification-before-completion/SKILL.md
+description: 'Release requirement after verify pass. Usage: /flow:release "REQ-123" [--janitor-hours N]'
+skill: workflow/flow-release
 ---
 
-# Flow-Release - 发布管理命令
+# Flow-Release Command (Harness Release)
 
-> Git 分支/PR/合并由用户自行管理，DevFlow 仅负责进度更新和提交。
+> 触发入口：执行细节由 `.claude/skills/workflow/flow-release/SKILL.md` 定义。
 
 ## User Input
+
 ```text
-$ARGUMENTS = "REQ_ID?"
+$ARGUMENTS = "REQ_ID [--janitor-hours N]"
 ```
-未提供则根据 `DEVFLOW_REQ_ID` 或 `.current-req` 自动解析。
 
-## 执行流程
+## Usage
 
-### 阶段 1: Entry Gate
-```
-1. 解析 REQ_ID
-2. {SCRIPT:prereq} --json 校验:
-   → 存在 PRD.md、EPIC.md、TASKS.md、TEST_REPORT.md、SECURITY_REPORT.md
-   → orchestration_status.status ∈ {"quality_complete", "qa_complete", "release_failed"}
-3. {SCRIPT:check_tasks} --json 确认 remaining == 0
-4. 验证 Quality gate:
-   → TEST_REPORT.md / SECURITY_REPORT.md 中的 Gate 均为 PASS
-5. Commit 规范门禁（工作区不干净时）:
-   → 必须先执行 `/util/git-commit`（规则见 `.claude/commands/util/git-commit.md`）
-   → Commit message 必须遵循 Conventional Commits；多文件按同类变更拆分提交
-   → 提交完成后重新执行 Entry Gate，直到工作区干净
+```bash
+/flow:release "REQ-123"
+/flow:release "REQ-123" --janitor-hours 72
 ```
 
-### 阶段 2: 发布上下文准备
-```
-1. 收集元数据:
-   → REQ_ID, TITLE, commits, changed files, coverage, security 状态
-2. 汇总文档:
-   → PRD 成功指标、EPIC 范围、TASKS DoD
-3. 更新 orchestration_status:
-   → status = "release_in_progress"
-   → phase = "release"
-4. EXECUTION_LOG.md 记录发布启动
-```
+## Internal Execution
 
-### 阶段 3: release-manager Agent
-```
-Prompt 核心要求:
-  - 确认 Constitution 校验无 ERROR:
-      {SCRIPT:validate_constitution} --type all --severity error
-  - 生成 RELEASE_PLAN.md:
-      • 范围概览、风险评估、回滚策略、监控计划
-  - 建议标签、检查清单
-```
+1. `npm run harness:release -- --change-id <REQ_ID>`
+2. `npm run harness:janitor -- --hours <N>` (default: `72`)
 
-### 阶段 4: Progress Update
-```
-1. 更新 BACKLOG.md:
-   → 找到对应 REQ 条目，更新状态为 completed/released
-2. 更新 ROADMAP.md:
-   → 找到对应 REQ 条目，更新进度
-3. 更新 orchestration_status:
-   → status = "release_complete"
-   → completedSteps append "release"
-4. EXECUTION_LOG.md 记录发布完成
-```
-
-### 阶段 5: Commit Gate
-```
-1. 若 `git status --porcelain` 非空:
-   → 按 `/util/git-commit` 规范提交
-   → 格式: chore(release): complete ${REQ_ID} - ${TITLE}
-2. 可选: {SCRIPT:generate_status} 生成状态报告
-```
+## Output
 
-## 输出
-```
-✅ RELEASE_PLAN.md
-✅ BACKLOG.md (进度更新)
-✅ ROADMAP.md (进度更新)
-✅ orchestration_status.json 更新 (release_complete)
-✅ EXECUTION_LOG.md 发布记录
-✅ Changes committed (用户自行处理分支/PR/合并)
-```
+- `devflow/requirements/<REQ_ID>/RELEASE_NOTE.md`
+- `devflow/requirements/<REQ_ID>/harness-state.json` (`status: released`)
 
-## 错误处理
-- Quality Gate 失败或 Constitution ERROR → 立即终止，标记 status="release_failed"。
-- 工作区存在未提交改动且未按 `/util/git-commit` 规则处理 → 阻断发布。
+## Completion
 
-## 下一步
-1. 用户自行处理分支合并 / PR 创建。
-2. 反馈验证结果，必要时触发 `/flow-verify` 复检。
+- 主链闭环：`init → spec → dev → verify → release`

package/.claude/commands/flow/restart.md

@@ -1,6 +1,6 @@
 ---
 name: flow-restart
-description: 'Restart interrupted cc-devflow requirement development. Usage: /flow-restart "REQ-123" [--from=stage]'
+description: 'Restart interrupted cc-devflow requirement development. Usage: /flow:restart "REQ-123" [--from=stage]'
 scripts:
   prereq: .claude/scripts/check-prerequisites.sh
   recover: .claude/scripts/recover-workflow.sh
@@ -16,8 +16,9 @@ $ARGUMENTS = "REQ_ID [--from=stage] [--force] [--backup]"
 
 ## 支持阶段
 ```
-research | prd | planning | development | qa | release
+init | spec | dev | verify | release
 ```
+兼容别名：`research->init`、`prd/planning->spec`、`development->dev`、`qa/quality->verify`。
 
 ## 执行流程
 
@@ -43,11 +44,10 @@ research | prd | planning | development | qa | release
 ### 阶段 2: 清理与重置
 ```
 1. 根据阶段执行清理动作:
-   • research: 清理临时 research/mcp 缓存、保留 summary
-   • prd: 备份 PRD.md，重置 status=initialized
-   • planning: 备份 EPIC.md/TASKS.md，清理规划中间状态
-   • development: 检查未完成任务、生成 git stash 建议
-   • qa: 删除过期 TEST_REPORT/SECURITY_REPORT
+   • init: 清理临时 research/mcp 缓存、保留 summary
+   • spec: 备份 PRD.md/EPIC.md/TASKS.md，重置 planning 状态
+   • dev: 检查未完成任务、生成 git stash 建议
+   • verify: 删除过期 TEST_REPORT/SECURITY_REPORT
    • release: 关闭未完成 PR 草稿、重置 release 状态
 
 2. 更新 orchestration_status:
@@ -61,12 +61,11 @@ research | prd | planning | development | qa | release
 ### 阶段 3: 恢复执行
 ```
 1. 根据 stage 自动触发后续命令提示：
-   → research → 建议运行 /flow-init --resume
-   → prd → /flow-prd
-   → planning → /flow-epic
-   → development → /flow-dev
-   → quality → /flow-quality（必要时追加 --full）
-   → release → /flow-release
+   → init（兼容 research）→ `/flow:init "REQ_ID|TITLE|URLS?"`
+   → spec（兼容 prd/planning）→ `/flow:spec "REQ_ID"`
+   → dev（兼容 development）→ `/flow:dev "REQ_ID" --resume`
+   → verify（兼容 qa/quality）→ `/flow:verify "REQ_ID" --strict`
+   → release → `/flow:release "REQ_ID"`
 
 2. 若 {SCRIPT:recover} 支持自动修复（如重建 TASKS），执行对应脚本。
 ```
@@ -81,7 +80,7 @@ research | prd | planning | development | qa | release
 ```
 
 ## 错误处理
-- 检测不到中断 → 提示使用 `/flow-status` 查看当前状态，或需 --force。
+- 检测不到中断 → 提示使用 `/flow:status` 查看当前状态，或需 --force。
 - 备份失败 → 终止并保留原样。
 - 清理动作报错 → 输出日志路径，允许用户手动处理后重试。
 
@@ -94,5 +93,5 @@ research | prd | planning | development | qa | release
 
 ## 下一步
 1. 按提示执行下一阶段命令。
-2. 使用 `/flow-status REQ_ID --detailed` 确认状态恢复正确。
-3. 如多次失败，考虑跑 `/flow-verify` 或手动 review 产物。
+2. 使用 `/flow:status REQ_ID --detailed` 确认状态恢复正确。
+3. 如多次失败，考虑跑 `/flow:verify` 或手动 review 产物。