cc-devflow 4.1.5 → 4.2.0

package/.claude/commands/flow/checklist.md

@@ -1,260 +1,18 @@
 ---
 name: flow-checklist
-description: 'Generate requirement quality checklist. Usage: /flow-checklist [OPTIONS]'
+description: 'Deprecated. Checklist stage merged into /flow:verify gates.'
 ---
 
-# /flow-checklist - 需求质量检查命令
+# /flow:checklist (Deprecated)
 
-## Usage
-```
-/flow-checklist [OPTIONS]
-```
+`/flow:checklist` 已废弃。
 
-## Purpose
-生成和管理需求质量检查清单 - "Unit Tests for English"。
-对需求文档进行质量测试，确保需求完整性、清晰性、一致性、可测量性和场景覆盖。
+## Migration
 
-## Options
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `--type` | string | `general` | Checklist 类型，支持逗号分隔多类型 |
-| `--status` | flag | - | 显示完成度统计 |
-| `--mark` | string | - | 批量标记检查项为完成 (CHK001,CHK002) |
-| `--mark-all` | flag | - | 标记所有检查项为完成 |
-| `--file` | string | - | 指定操作的 Checklist 文件 |
-| `--help` | flag | - | 显示帮助信息 |
+- 使用：`/flow:verify "REQ-123"`
+- 严格模式：`/flow:verify "REQ-123" --strict`
 
-## Valid Types
-- `ux`: UX/UI 需求检查
-- `api`: API 需求检查
-- `security`: 安全需求检查
-- `performance`: 性能需求检查
-- `data`: 数据需求检查
-- `general`: 通用需求检查 (默认)
+## Reason
 
-## Entry Gate
-1. 验证 `PRD.md` 存在
-2. 验证 `orchestration_status.json.prd_complete == true`
-3. 创建 `checklists/` 目录 (如不存在)
-
-## Execution Flow
-
-### Generate Checklist (--type)
-
-```
-1. Parse --type parameter
-   → Split by comma if multiple types
-   → Validate each type against valid_types
-
-2. For each type:
-   a. Read PRD.md content
-   b. Invoke checklist-agent.md with:
-      - prd_content: PRD.md 内容
-      - type: Checklist 类型
-      - config: quality-rules.yml 配置
-   c. Agent generates checklist items (15-30 items)
-   d. Write to checklists/{type}.md
-   e. If file exists: Append mode (继续编号)
-
-3. Output summary:
-   → Items generated per type
-   → Dimension coverage (5/5)
-   → Traceability percentage
-
-4. Update orchestration_status.json:
-   → checklist.generated_types[]
-   → checklist.total_items
-   → checklist.generated_at
-```
-
-### Check Status (--status)
-
-```
-1. Run calculate-checklist-completion.sh --json
-   → Scan checklists/*.md
-   → Count [x] and [ ] items
-
-2. Display completion table:
-   | Checklist | Complete | Total | Percentage |
-   |-----------|----------|-------|------------|
-   | ux.md     | 16       | 20    | 80%        |
-   | OVERALL   | 46       | 57    | 81%        |
-
-3. Compare to threshold (from quality-rules.yml)
-   → PASS: completion >= threshold
-   → FAIL: completion < threshold
-
-4. Update orchestration_status.json:
-   → checklist.checked_items
-   → checklist.completion_percentage
-   → checklist.last_check_at
-```
-
-### Mark Items (--mark)
-
-```
-1. Parse --mark parameter
-   → Split by comma
-   → Validate each ID format (CHK + 3 digits)
-
-2. For each ID:
-   a. Search checklists/*.md for CHK{NNN}
-   b. If found: Replace "- [ ]" with "- [x]"
-   c. If not found: Output warning
-
-3. Output:
-   → "Updated completion: N items marked"
-   → "Run /flow-checklist --status to see updated completion"
-```
-
-### Mark All (--mark-all --file)
-
-```
-1. Validate --file parameter exists
-2. Read specified file
-3. Replace all "- [ ]" with "- [x]"
-4. Output item count
-```
-
-## Exit Gate
-1. 如果生成了新 Checklist:
-   - 更新 `orchestration_status.json.checklist`
-   - 追加事件到 `EXECUTION_LOG.md`
-2. 输出下一步提示
-
-## Output Examples
-
-### Generate Single Type
-```
-Generating UX Checklist...
-Reading PRD.md...
-Analyzing UX requirements...
-Applying Anti-Example rules...
-
-✅ Generated: checklists/ux.md
-   Items: 18
-   Dimensions: 5/5 (Completeness, Clarity, Consistency, Measurability, Coverage)
-   Traceability: 85% (>=80% required)
-
-Next: Review and check items, then run /flow-checklist --status
-```
-
-### Generate Multiple Types
-```
-Generating multiple Checklists...
-
-[1/3] UX Checklist...
-✅ Generated: checklists/ux.md (18 items)
-
-[2/3] API Checklist...
-✅ Generated: checklists/api.md (22 items)
-
-[3/3] Security Checklist...
-✅ Generated: checklists/security.md (15 items)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Summary:
-| Type     | Items Generated | Coverage |
-|----------|-----------------|----------|
-| ux       | 18              | 5/5      |
-| api      | 22              | 5/5      |
-| security | 15              | 4/5      |
-| TOTAL    | 55              | -        |
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Next: Review and check items, then run /flow-checklist --status
-```
-
-### Check Status
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Checklist Completion Status
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-| Checklist | Complete | Total | Percentage |
-|-----------|----------|-------|------------|
-| ux.md     | 16       | 20    | 80%        |
-| api.md    | 18       | 22    | 82%        |
-| security  | 12       | 15    | 80%        |
-|-----------|----------|-------|------------|
-| OVERALL   | 46       | 57    | 81%        |
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Gate Threshold: 80%
-Status: ✅ PASS (81% >= 80%)
-
-Ready for: /flow-epic
-```
-
-## Error Handling
-
-### MISSING_PRD
-```
-ERROR: MISSING_PRD
-PRD.md not found in requirement directory.
-
-Run /flow-prd first.
-```
-
-### INVALID_TYPE
-```
-ERROR: INVALID_TYPE
-Invalid checklist type: {type}
-
-Valid types: ux, api, security, performance, data, general
-```
-
-### NO_CHECKLISTS
-```
-ERROR: NO_CHECKLISTS
-No checklists found in checklists/ directory.
-
-Run /flow-checklist --type <type> first.
-```
-
-## Append Mode (T011)
-
-When running `--type {type}` and `checklists/{type}.md` already exists:
-
-1. Read existing file
-2. Find highest CHK number (e.g., CHK018)
-3. Generate new items starting from next number (CHK019)
-4. Append new items to existing file
-5. Preserve existing structure and checked items
-
-## EXECUTION_LOG Events (T012)
-
-### Checklist Generated
-```markdown
-### 2025-12-15 23:55:00 (周日)
-**Event**: Checklist Generated
-**Type**: ux
-**Items**: 18
-**Dimensions**: 5/5
-**Traceability**: 85%
-```
-
-### Status Checked
-```markdown
-### 2025-12-15 23:58:00 (周日)
-**Event**: Checklist Status Checked
-**Completion**: 81%
-**Threshold**: 80%
-**Status**: PASS
-```
-
-## Related Commands
-
-| Command | Relationship |
-|---------|--------------|
-| `/flow-prd` | Prerequisite (generates PRD.md) |
-| `/flow-epic` | Consumer (uses checklist gate) |
-| `/flow-status` | Reader (displays checklist status) |
-
-## Configuration
-
-Config file: `config/quality-rules.yml`
-
-Key settings:
-- `gate.threshold`: Minimum completion % (default: 80)
-- `types.{type}.min_items`: Minimum items per type (default: 15)
-- `types.{type}.max_items`: Maximum items per type (default: 30)
+- Checklist 功能已并入 report-card 门禁模型。
+- 统一 gate 输出为 `devflow/requirements/<REQ_ID>/report-card.json`。

package/.claude/commands/flow/clarify.md

@@ -1,136 +1,18 @@
 ---
 name: flow-clarify
-description: 'Requirement clarification with 11-dimension ambiguity scan. Usage: /flow-clarify [REQ-XXX] [--skip] [--history]'
+description: 'Deprecated. Clarification step removed from default workflow. Use /flow:spec directly.'
 ---
 
-# /flow-clarify - 需求澄清命令
+# /flow:clarify (Deprecated)
 
-## Usage
-```
-/flow-clarify [REQ-XXX] [--skip] [--history]
-```
+`/flow:clarify` 已从默认主链移除。
 
-## Purpose
-在 PRD 生成前通过 11 维度歧义扫描系统化消除需求模糊性。
+## Migration
 
-## Arguments
-- `REQ-XXX`: 需求编号（可选，默认从分支推断）
-- `--skip`: 跳过澄清，直接进入下一阶段
-- `--history`: 查看历史澄清记录
+- 直接执行：`/flow:spec "REQ-123"`
+- 如需补充澄清，请将澄清结果写入：`devflow/requirements/<REQ_ID>/context-package.md`
 
-## Entry Gate
-1. 验证 `research/research.md` 存在
-2. 验证 `orchestration_status.json.phase0_complete == true`
-3. 检查 `.session.json` 是否有未完成会话（断点恢复）
+## Reason
 
-## Execution Flow
-
-### Phase 1: Scan (自动执行)
-```bash
-# 调用 run-clarify-scan.sh 执行 11 维度并行扫描
-.claude/scripts/run-clarify-scan.sh REQ-XXX --parallel
-```
-
-输出: scan_result.json (内存)
-
-### Phase 2: Question Generation (自动执行)
-```bash
-# 基于扫描结果生成 ≤5 个优先级排序问题
-.claude/scripts/generate-clarification-questions.sh --input scan_result.json --max 5
-```
-
-输出: questions[] with AI recommendations
-
-### Phase 3: Interactive Q&A (用户交互)
-For each question:
-1. Display question + options + AI recommendation (⭐ RECOMMENDED)
-2. Read user input
-3. Validate answer (A-E or ≤5 words)
-4. Generate rationale (Claude Haiku)
-5. Save to .session.json (incremental)
-
-### Phase 4: Report Generation (自动执行)
-```bash
-# 生成澄清报告
-.claude/scripts/generate-clarification-report.sh --session .session.json
-```
-
-输出: research/clarifications/[timestamp]-flow-clarify.md
-
-## Exit Gate
-1. 验证报告完整性
-2. 更新 `orchestration_status.json`:
-   - `clarify_complete = true`
-   - `clarify_session_id = [sessionId]`
-3. 删除 `.session.json`
-4. 输出: "✅ Ready for /flow-prd"
-
-## Session Recovery
-如果检测到 `.session.json`:
-1. 显示恢复提示
-2. 从 `currentQuestionIndex` 继续
-3. 不重复已回答的问题
-
-## User Abort (Ctrl+C)
-1. 捕获 SIGINT
-2. 保存当前进度到 `.session.json`
-3. 输出恢复命令: `/flow-clarify REQ-XXX`
-
-## Output Format
-
-### Question Display
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📝 Q1: 关于 Functional Scope
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-用户权限应如何划分？
-
-  A) RBAC 角色模型 - 基于角色的访问控制
-  B) ABAC 属性模型 - 基于属性的访问控制
-  C) 简单二元权限 - admin/user 两级
-
-  ⭐ RECOMMENDED: A (RBAC 是企业级应用最常见模式)
-
-Your choice (A-C, or press Enter for recommended):
-```
-
-### Report Structure
-```markdown
-# Clarification Report: REQ-XXX
-
-## Metadata
-- Session ID: 20251215-143000-REQ-001
-- Date: 2025-12-15
-- Questions: 3 / 5
-
-## Scan Summary
-| Dimension | Status | Issues |
-|-----------|--------|--------|
-| Functional Scope | ambiguous | 2 |
-| ...
-
-## Clarification Session
-### Q1: Functional Scope
-**Question**: 用户权限应如何划分？
-**Answer**: A (RBAC 角色模型)
-**Rationale**: RBAC 提供灵活的权限管理...
-
-## Next Command
-✅ Run `/flow-prd` to generate PRD
-```
-
-## Error Handling
-- `MISSING_RESEARCH`: research.md 不存在 → 提示先运行 `/flow-init`
-- `INVALID_PHASE`: phase0_complete != true → 提示完成研究阶段
-- `API_ERROR`: Claude API 错误 → 降级到规则引擎
-- `SESSION_CORRUPT`: .session.json 损坏 → 提示删除重试
-
-## Related Commands
-- **前置**: `/flow-init` (生成 research.md)
-- **后续**: `/flow-prd` (生成 PRD)
-- **可选**: `/flow-clarify --history` (查看历史)
-
-## Constitution Compliance
-- **Article I**: 完整实现，无 TODO
-- **Article III**: API Key 使用环境变量
-- **Article VI**: TDD 顺序正确
+- 独立澄清阶段导致链路变长且可恢复点分散。
+- 主链改为 `init -> spec -> dev -> verify -> release`。

package/.claude/commands/flow/constitution.md

@@ -79,4 +79,4 @@ $ARGUMENTS = "[--article I] [--verify] [--impact-report] [--amend --proposal pat
 
 ## 下一步
 - 需要向项目传播修订时，先运行 `--impact-report`，与团队确认后再 `--apply`。
-- 应用后建议运行 `/flow-verify --all` 确认所有需求遵循最新宪法。
+- 应用后建议运行 `/flow:verify --strict` 确认所有需求遵循最新宪法。

package/.claude/commands/flow/context.md

@@ -102,7 +102,7 @@ Overall: 12/13 paths valid (92%)
 
 ### With flow-init
 
-When `/flow-init` creates a new requirement, it automatically runs:
+When `/flow:init` creates a new requirement, it automatically runs:
 ```bash
 /flow-context init {REQ-ID} --type {detected-type}
 ```