cc-devflow 4.1.4 → 4.1.6

package/.claude/skills/cc-devflow-orchestrator/SKILL.md

@@ -6,159 +6,139 @@ description: CC-DevFlow workflow router and agent recommender. Use when starting
 # CC-DevFlow Orchestrator
 
 ## Purpose
-Guide users to the correct agent/command WITHOUT duplicating their detailed standards.
+Guide users to the correct command/skill without duplicating detailed implementation standards.
 
 ## Workflow Map
 
-### 🏢 项目级工作流（Project-Level, 项目初期执行一次）
+### Project-Level (run once per project)
 
-```
-/core:roadmap → ROADMAP.md + BACKLOG.md (产品路线图)
-/core:architecture → ARCHITECTURE.md (系统架构设计)
-/core:guidelines → frontend-guidelines.md / backend-guidelines.md (项目规范)
-/core:style → STYLE.md (设计风格指南)
+```text
+/core:roadmap      → ROADMAP.md + BACKLOG.md
+/core:architecture → ARCHITECTURE.md
+/core:guidelines   → frontend/backend guidelines
+/core:style        → STYLE.md
 ```
 
-### 📦 需求级工作流（Requirement-Level, 每个需求执行一次）
+### Requirement-Level Canonical Mainline (v6)
 
-```
-/flow:init → research.md + tasks.json + BRAINSTORM.md (研究初始化 + 头脑风暴)
-     ↓
-/flow:clarify → clarifications/*.md (11 维度歧义扫描, 可选)
+```text
+/flow:init    → harness:init + harness:pack
+             → context-package.md + harness-state.json
      ↓
-/flow:spec → PRD + Tech + UI + Epic (统一规格阶段)
-  Modes:
-  - Full: PRD → Tech+UI (并行) → Epic
-  - Quick: PRD → Epic (--skip-tech --skip-ui)
-  - Backend: PRD → Tech → Epic (--skip-ui)
-  - Frontend: PRD → UI → Epic (--skip-tech)
+/flow:spec    → harness:plan
+             → task-manifest.json
      ↓
-/flow:dev → TASKS.md execution (TDD + Autonomous mode default)
+/flow:dev     → harness:dispatch / harness:resume
+             → runtime events + checkpoints + manifest status
      ↓
-/flow:quality → Quality verification
+/flow:verify  → harness:verify
+             → report-card.json (quick/strict gates)
      ↓
-/flow:release → PR creation + deployment
-     ↓
-/flow:verify → consistency check (任意阶段可调用)
-```
-
-### 🚀 简化流程
-
+/flow:release → harness:release + harness:janitor
+             → RELEASE_NOTE.md + released state
 ```
-【精简流程】(适合小需求, 3 步)
-/flow:init --quick → /flow:spec --skip-tech --skip-ui → /flow:dev → /flow:release
 
-【标准流程】(适合中等需求, 4 步)
-/flow:init → /flow:spec → /flow:dev → /flow:quality → /flow:release
+### Bug Workflow
 
-【完整流程】(适合大需求, 5 步)
-/flow:init → /flow:clarify → /flow:spec → /flow:dev → /flow:quality --full → /flow:release
+```text
+/flow:fix "BUG-123|描述" → 系统化调试与修复
 ```
 
-### 🐛 Bug 修复工作流
+### Deprecated Migrations (keep for compatibility)
 
+```text
+/flow:new       → /flow:init → /flow:spec → /flow:dev → /flow:verify → /flow:release
+/flow:clarify   → merged into /flow:spec
+/flow:checklist → merged into /flow:verify --strict
+/flow:quality   → merged into /flow:verify
 ```
-/flow:fix "BUG-123|描述" → 系统化调试 (4阶段: Root Cause → Pattern → Hypothesis → TDD Fix)
-```
-
-**说明**:
-- `/flow:spec` 是统一规格命令，合并 PRD/Tech/UI/Epic 为单一命令
-- `/flow:spec` 内部并行执行 Tech + UI，减少 ~35% 设计阶段时间
-- `/flow:dev` 默认 Autonomous 模式（自动重试），使用 `--manual` 退出到 Manual 模式
 
-## Agent Delegation Guide
+## Routing Guide
 
-### When User Asks About Unified Specification
-- **DO**: Recommend `/flow:spec` command → orchestrates prd-writer + tech-architect + ui-designer + planner
-- **Link**: See `.claude/skills/workflow/flow-spec/SKILL.md` for details
-- **Modes**: Full (default), Quick (--skip-tech --skip-ui), Backend (--skip-ui), Frontend (--skip-tech)
+### Requirement kickoff
+- Recommend: `/flow:init "REQ-123|Title|URLs?"`
+- Then: `/flow:spec "REQ-123"`
 
-### When User Asks About Requirements Clarification
-- **DO**: Recommend `/flow:clarify` command → invokes clarify-analyst agent
-- **Link**: See `.claude/commands/flow/clarify.md` for details
+### Planning/specification questions
+- Recommend: `/flow:spec`
+- Notes: this is the unified planning stage for executable task-manifest generation.
 
-### When User Asks About PRD/Tech/UI/Epic
-- **DO**: Recommend `/flow:spec` command (unified)
-- **Link**: See `.claude/agents/prd-writer.md`, `tech-architect.md`, `ui-designer.md`, `planner.md` for agent details
+### Development execution / interrupted execution
+- Recommend: `/flow:dev "REQ-123"`
+- If interrupted/failed: `/flow:dev "REQ-123" --resume`
 
-### When User Asks About QA/Security
-- **DO**: Recommend `/flow:quality` command → invokes qa-tester + security-reviewer agents
-- **Link**: See `.claude/agents/qa-tester.md` for QA details
+### QA/security/release readiness
+- Recommend: `/flow:verify "REQ-123"`
+- Strict gate: `/flow:verify "REQ-123" --strict`
 
-### When User Asks About Code Review
-- **DO**: Recommend `/flow:review` command → invokes spec-reviewer + code-quality-reviewer agents
-- **Link**: See `.claude/commands/flow/review.md` for details
+### Release
+- Recommend: `/flow:release "REQ-123"`
+- Release is blocked when report-card overall is fail.
 
-### When User Asks About Bug Fix
-- **DO**: Recommend `/flow:fix` command → 4-phase systematic debugging
-- **Link**: See `.claude/commands/flow/fix.md` for details
+### Code review requests
+- Recommend: `/flow:verify "REQ-123" --strict`
+- Optional deep review: `/util:code-review "<diff>"`
 
 ## Phase Gates (Quick Reference)
 
 ### Entry Gates
-- **flow:init Entry**: Git 工作区干净, main 分支
-- **flow:clarify Entry**: research.md 存在, phase0_complete == true
-- **flow:spec Entry**: BRAINSTORM.md 存在, research.md 无 TODO placeholder
-- **flow:dev Entry**: EPIC.md + TASKS.md 存在
-- **flow:quality Entry**: development_complete == true
-- **flow:release Entry**: quality_complete == true
+- `flow:init`: repository and requirement id are valid.
+- `flow:spec`: `context-package.md` and `harness-state.json` exist.
+- `flow:dev`: `task-manifest.json` exists and is schema-valid.
+- `flow:verify`: task dispatch completed or at least one dispatch/resume run exists.
+- `flow:release`: `report-card.json.overall == pass`.
 
 ### Exit Gates
-- **flow:init Exit**: research.md 5-level quality check, BRAINSTORM.md 完整
-- **flow:spec Exit**: PRD.md + EPIC.md + TASKS.md 完整, TDD 顺序正确
-- **flow:dev Exit**: 所有 TASKS 完成, TDD Checkpoint 通过
-- **flow:quality Exit**: 无 high-severity 漏洞
-- **flow:release Exit**: PR 创建成功
+- `flow:init`: requirement context packaged.
+- `flow:spec`: task-manifest generated.
+- `flow:dev`: task statuses updated with runtime checkpoints/events.
+- `flow:verify`: report-card emitted (quick/strict/review sections).
+- `flow:release`: release note generated and harness state marked released.
 
-## State Machine: Status → Recommended Command
+## State → Recommended Command
 
 ```yaml
-status: "initialized"
-  → Recommend: /flow:spec (统一规格阶段)
-  → Alternative: /flow:clarify (optional)
+no_requirement_context:
+  recommend: /flow:init
 
-status: "clarify_complete" OR "clarify_skipped"
-  → Recommend: /flow:spec
+initialized_or_context_packed:
+  recommend: /flow:spec
 
-status: "spec_complete"
-  → Recommend: /flow:dev (TDD development, Autonomous mode default)
+manifest_exists_with_pending_or_failed:
+  recommend: /flow:dev
+  alternative: /flow:dev --resume
 
-status: "development_complete"
-  → Recommend: /flow:quality
+manifest_all_passed_without_report_card:
+  recommend: /flow:verify --strict
 
-status: "quality_complete"
-  → Recommend: /flow:release
+report_card_fail:
+  recommend: /flow:dev --resume
+  then: /flow:verify --strict
 
-status: "released"
-  → Recommend: /flow:verify (final consistency check)
+report_card_pass:
+  recommend: /flow:release
+
+released:
+  recommend: /flow:archive (optional)
 ```
 
 ## Auxiliary Commands
 
-### Status and Progress
-- `/flow:status` - Query requirement progress
-- `/flow:update "REQ-123" "T012"` - Update task completion
-- `/flow:restart "REQ-123" --from=spec` - Resume interrupted workflow
-
-### Upgrade and Analysis
-- `/flow:upgrade "REQ-123" --analyze` - PRD version upgrade impact analysis
-- `/flow:constitution` - Constitution management
-- `/flow:verify "REQ-123"` - Comprehensive consistency verification
-
-### Bug Fix
-- `/flow:fix "BUG-123|描述"` - 系统化 BUG 修复
-- `/util:problem-analyzer "<issue>"` - Problem diagnosis
+### Progress and recovery
+- `/flow:status` - query requirement progress
+- `/flow:update "REQ-123" "T012"` - update task progress
+- `/flow:restart "REQ-123" --from=dev` - recover interrupted workflow state
 
-### Code Review
-- `/flow:review "REQ-123"` - Two-Stage Code Review
-- `/util:code-review "<diff>"` - High-rigor code review
+### Upgrade and governance
+- `/flow:upgrade "REQ-123" --analyze` - PRD version impact analysis
+- `/flow:constitution` - constitution governance
+- `/flow:verify "REQ-123"` - consistency and quality verification
 
 ## Design Principle
 
-**This skill ONLY contains**:
-- ✅ Workflow routing (which command to run next)
-- ✅ Agent delegation (which agent handles what)
-- ✅ Quick reference (Phase Gates summary)
-- ✅ Links to detailed documentation
+This skill only does routing:
+- Which command to run next
+- Which gate blocks progress
+- Which migration path applies for deprecated commands
 
-**Rationale**: Avoid duplication. Agents and Commands own detailed standards.
+Detailed quality standards stay in command files and workflow skills.

package/.claude/skills/workflow/CLAUDE.md

@@ -0,0 +1,24 @@
+# workflow/
+> L2 | 父级: /Users/dimon/001Area/80-CodeWorld/002-devflow/cc-devflow/.claude/CLAUDE.md
+
+成员清单
+flow-init/SKILL.md: 需求初始化入口，调用 harness:init + harness:pack。
+flow-init/context.jsonl: flow-init 的上下文注入定义。
+flow-spec/SKILL.md: 计划生成入口，调用 harness:plan 产出 task-manifest。
+flow-spec/context.jsonl: flow-spec 的上下文注入定义。
+flow-spec/team-config.json: 旧 Team 配置资产（兼容保留，当前主链不依赖）。
+flow-dev/SKILL.md: 执行入口，调用 harness:dispatch/resume 并写 checkpoint/events。
+flow-dev/context.jsonl: flow-dev 的上下文注入定义。
+flow-dev/dev-implementer.jsonl: 旧 dev-implementer 上下文（兼容保留）。
+flow-verify/SKILL.md: 质量门禁入口，调用 harness:verify 输出 report-card。
+flow-verify/context.jsonl: flow-verify 的上下文注入定义。
+flow-release/SKILL.md: 发布入口，调用 harness:release + harness:janitor。
+flow-release/context.jsonl: flow-release 的上下文注入定义。
+flow-quality/SKILL.md: 旧质量流程技能（迁移过渡保留）。
+flow-quality/context.jsonl: 旧质量流程上下文（迁移过渡保留）。
+flow-fix/SKILL.md: Bug 修复流程技能。
+flow-fix/context.jsonl: flow-fix 的上下文注入定义。
+
+法则: 成员完整·一行一文件·父级链接·技术词前置
+
+[PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/skills/workflow/flow-dev/CLAUDE.md

@@ -1,78 +1,16 @@
-# flow-dev/ - Development Execution Skill
-
-> L2 | 父级: `.claude/skills/workflow/CLAUDE.md`
-
-## Purpose
-
-执行开发任务，遵循 TDD Iron Law，默认 Autonomous 模式。
-
-## Members
-
-| File | Purpose | Lines |
-|------|---------|-------|
-| `SKILL.md` | 核心指令：TDD 执行流程、模式、错误处理 | ~100 |
-| `context.jsonl` | 通用上下文注入定义 (fallback) | ~10 |
-| `dev-implementer.jsonl` | dev-implementer Agent 专用上下文 [NEW: v4.4] | ~10 |
-| `scripts/entry-gate.sh` | 入口检查：TASKS.md 存在、状态验证 | ~100 |
-| `scripts/exit-gate.sh` | 出口检查：任务完成度、测试验证 | ~100 |
-| `scripts/task-orchestrator.sh` | 任务调度：解析 TASKS.md、标记完成 | ~100 |
-| `references/dev-implementer.md` | Agent 指令链接 | symlink |
-| `assets/IMPLEMENTATION_PLAN_TEMPLATE.md` | 实现计划模板 | ~80 |
-
-## Context Injection (v4.4)
-
-Hook `inject-agent-context.ts` 在 Task 调用前自动注入上下文：
-
-```
-Task(subagent_type="dev-implementer", prompt="...")
-    ↓
-Hook 检测到 dev-implementer
-    ↓
-读取 dev-implementer.jsonl
-    ↓
-解析 JSONL，加载文件内容
-    ↓
-注入到 prompt 中
-```
-
-JSONL 格式 (Trellis 风格):
-```jsonl
-{"file": "devflow/requirements/{REQ}/TASKS.md", "reason": "Task list with DoD"}
-{"file": "devflow/spec/frontend/index.md", "reason": "Frontend conventions", "optional": true}
-```
-
-## TDD Iron Law
-
-```
-NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
-```
-
-## Execution Flow
-
-```
-Entry Gate → Task Loop (TDD) → Exit Gate
-
-For each task:
-  1. Protocol 2: 读取任务 DoD
-  2. Write failing test (Phase 2)
-  3. Verify test fails
-  4. Write implementation (Phase 3)
-  5. Verify test passes
-  6. Mark task [x]
-  7. Protocol 3: 读取下一任务 + ERROR_LOG
-```
-
-## Mode Matrix
-
-| Mode | Flag | Behavior |
-|------|------|----------|
-| Autonomous | (default) | 自动重试，迭代直到完成 |
-| Manual | `--manual` | 遇错停止，等待用户 |
-
-## Agent Reference
-
-- `references/dev-implementer.md` → `.claude/agents/dev-implementer.md`
-
----
+# flow-dev/
+> L2 | 父级: /Users/dimon/001Area/80-CodeWorld/002-devflow/cc-devflow/.claude/skills/workflow/CLAUDE.md
+
+成员清单
+SKILL.md: flow:dev 的核心指令，定义 dispatch/resume 的参数与失败恢复策略。
+context.jsonl: flow-dev 上下文注入定义（task-manifest/context-package/runtime）。
+dev-implementer.jsonl: 旧 Agent 上下文（兼容保留，非主链关键路径）。
+scripts/entry-gate.sh: 旧入口脚本资产（兼容保留）。
+scripts/exit-gate.sh: 旧出口脚本资产（兼容保留）。
+scripts/task-orchestrator.sh: 旧任务调度脚本资产（兼容保留）。
+assets/IMPLEMENTATION_PLAN_TEMPLATE.md: 旧实现计划模板资产（兼容保留）。
+references/dev-implementer.md: 旧 Agent 指令引用（兼容保留）。
+
+法则: 成员完整·一行一文件·父级链接·技术词前置
 
 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/skills/workflow/flow-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: flow-dev
-description: 'Execute development tasks with TDD and Autonomous mode. Usage: /flow-dev "REQ-123" [--manual] [--max-iterations N]'
+description: 'Execute task-manifest with dependency-aware parallel dispatch and checkpoint recovery. Use when implementing planned tasks for a requirement.'
 ---
 
 # Flow-Dev Skill
@@ -9,88 +9,50 @@ description: 'Execute development tasks with TDD and Autonomous mode. Usage: /fl
 
 ## Purpose
 
-执行开发任务，遵循 TDD Iron Law，默认 Autonomous 模式。
-
-## TDD Iron Law
-
-```
-NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
-```
-
-### TDD Checkpoint
-
-```yaml
-⚠️ TEST VERIFICATION CHECKPOINT:
-  1. 运行所有 Phase 2 测试
-  2. 验证所有新测试 FAIL
-  3. 只有全部 FAIL 后才能进入 Phase 3
-  4. 如果已经写了实现代码 → DELETE 重来
-```
+执行 `task-manifest.json` 中的任务，默认并行调度并写入 checkpoint/events 供恢复。
 
 ## Input Format
 
+```bash
+/flow:dev "REQ_ID" [--parallel N] [--resume] [--max-retries N]
 ```
-/flow-dev "REQ_ID" [--manual] [--max-iterations N] [--task T###]
-```
-
-- **默认**: Autonomous 模式 (自动重试)
-- **--manual**: Manual 模式 (遇错停止)
-- **--max-iterations**: 最大迭代次数 (默认 10)
-- **--task**: 从指定任务开始
 
-## 运行模式对比
+## Execution Steps
 
-| | Manual | Autonomous (默认) |
-|--|--------|------------------|
-| 遇到错误 | 停止 | 自动重试 |
-| 注意力刷新 | Protocol 2 | Protocol 2+3+4 |
-| 适用场景 | 复杂需求 | 清晰需求 |
-
-## Execution Flow
-
-### Stage 1: Entry Gate
-
-1. TASKS.md 存在
-2. EPIC.md 存在
-3. Status: `epic_complete`
-
-### Stage 2: Task Execution (Ralph Loop)
+1. 解析参数：
+   - 默认 `parallel = 3`
+   - 默认不 resume
+2. 分支执行：
+   - 普通执行：
 
-```
-For each task in TASKS.md:
-  1. Protocol 2: 读取任务 DoD
-  2. 执行任务
-  3. 验证完成
-  4. 标记 [x]
-  5. Protocol 3: 读取下一任务 + ERROR_LOG
+```bash
+npm run harness:dispatch -- --change-id "${REQ_ID}" --parallel ${PARALLEL} [--max-retries ${MAX_RETRIES}]
 ```
 
-### Stage 3: Error Handling
+   - 恢复执行：
 
-```
-On Error:
-  1. Protocol 4: 读取 ERROR_LOG.md
-  2. 记录错误到 ERROR_LOG.md
-  3. Autonomous: 自动重试
-  4. Manual: 停止等待
+```bash
+npm run harness:resume -- --change-id "${REQ_ID}" --parallel ${PARALLEL} [--max-retries ${MAX_RETRIES}]
 ```
 
-### Stage 4: Exit Gate
+3. 检查执行结果：
+   - `task-manifest.json` 状态更新
+   - `.harness/runtime/${REQ_ID}/<TASK_ID>/events.jsonl`
+   - `.harness/runtime/${REQ_ID}/<TASK_ID>/checkpoint.json`
 
-1. 所有任务完成
-2. 测试通过
-3. Status: `development_complete`
+## Exit Criteria
 
-## Attention Refresh Protocols
+- 所有任务状态为 `passed` 或 `skipped`
+- 没有 `running` 残留状态
 
-| Protocol | Trigger | Reads |
-|----------|---------|-------|
-| 2 | Task start | TASKS.md T### + DoD |
-| 3 | Iteration start | TASKS.md + ERROR_LOG |
-| 4 | After error | ERROR_LOG.md |
+## Failure Handling
+
+- 若存在 `failed` 任务：
+  1. 修复失败原因
+  2. 重新运行 `--resume`
 
 ## Next Step
 
-```
-/flow-quality "${REQ_ID}"
+```bash
+/flow:verify "${REQ_ID}"
 ```

package/.claude/skills/workflow/flow-dev/context.jsonl

@@ -1,8 +1,4 @@
-{"file": "devflow/requirements/{REQ}/TASKS.md", "reason": "Task list"}
-{"file": "devflow/requirements/{REQ}/EPIC.md", "reason": "Epic overview"}
-{"file": "devflow/requirements/{REQ}/BRAINSTORM.md", "reason": "Original intent"}
-{"file": "devflow/requirements/{REQ}/ERROR_LOG.md", "reason": "Previous errors", "optional": true}
-{"file": "devflow/requirements/{REQ}/TECH_DESIGN.md", "reason": "Technical design", "optional": true}
-{"file": "devflow/spec/frontend/index.md", "reason": "Frontend conventions", "optional": true}
-{"file": "devflow/spec/backend/index.md", "reason": "Backend conventions", "optional": true}
-{"file": ".claude/rules/project-constitution.md", "reason": "Quality rules"}
+{"file": "devflow/requirements/{REQ}/task-manifest.json", "reason": "Executable task graph"}
+{"file": "devflow/requirements/{REQ}/context-package.md", "reason": "Execution constraints", "optional": true}
+{"file": "devflow/requirements/{REQ}/harness-state.json", "reason": "Lifecycle status", "optional": true}
+{"file": ".claude/rules/project-constitution.md", "reason": "Quality rules and constraints"}