cc-devflow 4.1.5 → 4.1.6

package/.claude/scripts/recover-workflow.sh

@@ -28,24 +28,23 @@ usage() {
 
 选项:
   -h, --help              显示此帮助信息
-  --from STAGE            从指定阶段重新开始 (init/prd/epic/dev/quality/release, qa 兼容)
+  --from STAGE            从指定阶段重新开始 (init/spec/dev/verify/release；prd/epic/quality/qa 兼容)
   --force                 强制恢复，跳过安全检查
   --dry-run               显示恢复计划但不执行
   --verbose               显示详细信息
 
 阶段说明:
   init      - 初始化阶段
-  prd       - PRD生成阶段
-  epic      - Epic规划阶段
+  spec      - 规格与任务规划阶段
   dev       - 开发执行阶段
-  quality   - 质量验证阶段
+  verify    - 质量验证阶段
   release   - 发布管理阶段
 
 示例:
   $0 REQ-123                          # 自动检测并恢复
   $0 REQ-123 --from dev               # 从开发阶段重新开始
   $0 REQ-123 --dry-run                # 预览恢复计划
-  $0 REQ-123 --from prd --force       # 强制从PRD阶段重新开始
+  $0 REQ-123 --from spec --force      # 强制从规划阶段重新开始
 
 EOF
     exit 0
@@ -127,14 +126,14 @@ detect_workflow_status() {
     # 检查需求目录是否存在
     if [[ ! -d "$REQ_DIR" ]]; then
         echo -e "${RED}错误: 需求目录不存在: $REQ_DIR${NC}"
-        echo -e "${YELLOW}建议: 使用 /flow-init 初始化需求${NC}"
+        echo -e "${YELLOW}建议: 使用 /flow:init 初始化需求${NC}"
         exit 1
     fi
 
     # 检查状态文件
     if [[ ! -f "$STATUS_FILE" ]]; then
         echo -e "${YELLOW}警告: 状态文件不存在，需求可能未正确初始化${NC}"
-        echo -e "${YELLOW}建议: 使用 /flow-init --force 重新初始化${NC}"
+        echo -e "${YELLOW}建议: 使用 /flow:init --force 重新初始化${NC}"
         exit 1
     fi
 
@@ -213,29 +212,21 @@ analyze_recovery_strategy() {
     if [[ -n "$FROM_STAGE" ]]; then
         echo -e "${YELLOW}用户指定从阶段恢复: $FROM_STAGE${NC}"
         validate_stage "$FROM_STAGE"
-        echo "$FROM_STAGE"
+        echo "$(normalize_stage "$FROM_STAGE")"
         return 0
     fi
 
     # 根据当前阶段智能判断恢复点
     case "$current_phase" in
-        initialized|planning)
-            echo -e "${CYAN}建议: 从 PRD 阶段开始${NC}"
-            echo "prd"
+        initialized|context_packed|planning|planned|spec_in_progress)
+            echo -e "${CYAN}建议: 从规格阶段开始${NC}"
+            echo "spec"
             ;;
-        prd_generation_in_progress)
-            echo -e "${CYAN}建议: 重新生成 PRD${NC}"
-            echo "prd"
-            ;;
-        prd_complete|epic_planning)
-            echo -e "${CYAN}建议: 从 Epic 阶段开始${NC}"
-            echo "epic"
-            ;;
-        epic_complete)
+        prd_generation_in_progress|epic_planning|prd_complete|epic_complete|spec_complete)
             echo -e "${CYAN}建议: 从开发阶段开始${NC}"
             echo "dev"
             ;;
-        development|dev_complete)
+        development|development_in_progress|dev_complete|development_complete)
             # 检查是否有未完成的任务
             if [[ -f "$REQ_DIR/TASKS.md" ]]; then
                 # 统计已完成任务 (- [x] 标记)
@@ -252,16 +243,20 @@ analyze_recovery_strategy() {
                     echo "dev"
                 else
                     echo -e "${CYAN}建议: 进入质量验证阶段${NC}"
-                    echo "quality"
+                    echo "verify"
                 fi
             else
                 echo -e "${CYAN}建议: 从开发阶段开始${NC}"
                 echo "dev"
             fi
             ;;
-        quality|quality_complete|qa|qa_complete)
+        quality|qa|verification_in_progress)
             echo -e "${CYAN}建议: 从质量验证阶段开始${NC}"
-            echo "quality"
+            echo "verify"
+            ;;
+        quality_complete|qa_complete|verified)
+            echo -e "${CYAN}建议: 从发布阶段开始${NC}"
+            echo "release"
             ;;
         release|release_complete)
             echo -e "${CYAN}建议: 从发布阶段开始${NC}"
@@ -273,8 +268,8 @@ analyze_recovery_strategy() {
             exit 0
             ;;
         *)
-            echo -e "${YELLOW}警告: 未知阶段 '$current_phase'，从 PRD 开始${NC}"
-            echo "prd"
+            echo -e "${YELLOW}警告: 未知阶段 '$current_phase'，从规格阶段开始${NC}"
+            echo "spec"
             ;;
     esac
 }
@@ -284,17 +279,33 @@ validate_stage() {
     local stage="$1"
 
     case "$stage" in
-        init|prd|epic|dev|quality|qa|release)
+        init|spec|dev|verify|release|prd|epic|quality|qa)
             return 0
             ;;
         *)
             echo -e "${RED}错误: 无效的阶段 '$stage'${NC}"
-            echo -e "${YELLOW}有效阶段: init, prd, epic, dev, quality, release (qa 兼容)${NC}"
+            echo -e "${YELLOW}有效阶段: init, spec, dev, verify, release (prd/epic/quality/qa 兼容)${NC}"
             exit 1
             ;;
     esac
 }
 
+# 兼容历史阶段名称，统一映射到主链阶段
+normalize_stage() {
+    local stage="$1"
+    case "$stage" in
+        prd|epic)
+            echo "spec"
+            ;;
+        quality|qa)
+            echo "verify"
+            ;;
+        *)
+            echo "$stage"
+            ;;
+    esac
+}
+
 # ============================================================================
 # 恢复执行
 # ============================================================================
@@ -315,19 +326,16 @@ generate_recovery_plan() {
     local stages=()
     case "$start_stage" in
         init)
-            stages=("init" "prd" "epic" "dev" "quality" "release")
+            stages=("init" "spec" "dev" "verify" "release")
             ;;
-        prd)
-            stages=("prd" "epic" "dev" "quality" "release")
-            ;;
-        epic)
-            stages=("epic" "dev" "quality" "release")
+        spec)
+            stages=("spec" "dev" "verify" "release")
             ;;
         dev)
-            stages=("dev" "quality" "release")
+            stages=("dev" "verify" "release")
             ;;
-        quality|qa)
-            stages=("quality" "release")
+        verify)
+            stages=("verify" "release")
             ;;
         release)
             stages=("release")
@@ -340,22 +348,19 @@ generate_recovery_plan() {
         local command=""
         case "$stage" in
             init)
-                command="/flow-init \"$REQ_ID\""
-                ;;
-            prd)
-                command="/flow-prd \"$REQ_ID\""
+                command="/flow:init \"$REQ_ID\""
                 ;;
-            epic)
-                command="/flow-epic \"$REQ_ID\""
+            spec)
+                command="/flow:spec \"$REQ_ID\""
                 ;;
             dev)
-                command="/flow-dev \"$REQ_ID\" --resume"
+                command="/flow:dev \"$REQ_ID\" --resume"
                 ;;
-            quality)
-                command="/flow-quality \"$REQ_ID\""
+            verify)
+                command="/flow:verify \"$REQ_ID\" --strict"
                 ;;
             release)
-                command="/flow-release \"$REQ_ID\""
+                command="/flow:release \"$REQ_ID\""
                 ;;
         esac
 
@@ -387,43 +392,35 @@ execute_recovery() {
     fi
 
     # 根据起始阶段执行命令
-    # 注意: 这里只是展示命令，实际执行由用户手动调用或使用 /flow-restart
+    # 注意: 这里只是展示命令，实际执行由用户手动调用或使用 /flow:restart
     echo -e "${CYAN}请手动执行以下命令以恢复工作流:${NC}"
     echo ""
 
     case "$start_stage" in
         init)
-            echo "/flow-init \"$REQ_ID\""
-            echo "/flow-prd \"$REQ_ID\""
-            echo "/flow-epic \"$REQ_ID\""
-            echo "/flow-dev \"$REQ_ID\""
-            echo "/flow-quality \"$REQ_ID\""
-            echo "/flow-release \"$REQ_ID\""
+            echo "/flow:init \"$REQ_ID\""
+            echo "/flow:spec \"$REQ_ID\""
+            echo "/flow:dev \"$REQ_ID\""
+            echo "/flow:verify \"$REQ_ID\" --strict"
+            echo "/flow:release \"$REQ_ID\""
             ;;
-        prd)
-            echo "/flow-prd \"$REQ_ID\""
-            echo "/flow-epic \"$REQ_ID\""
-            echo "/flow-dev \"$REQ_ID\""
-            echo "/flow-quality \"$REQ_ID\""
-            echo "/flow-release \"$REQ_ID\""
-            ;;
-        epic)
-            echo "/flow-epic \"$REQ_ID\""
-            echo "/flow-dev \"$REQ_ID\""
-            echo "/flow-quality \"$REQ_ID\""
-            echo "/flow-release \"$REQ_ID\""
+        spec)
+            echo "/flow:spec \"$REQ_ID\""
+            echo "/flow:dev \"$REQ_ID\""
+            echo "/flow:verify \"$REQ_ID\" --strict"
+            echo "/flow:release \"$REQ_ID\""
             ;;
         dev)
-            echo "/flow-dev \"$REQ_ID\" --resume"
-            echo "/flow-quality \"$REQ_ID\""
-            echo "/flow-release \"$REQ_ID\""
+            echo "/flow:dev \"$REQ_ID\" --resume"
+            echo "/flow:verify \"$REQ_ID\" --strict"
+            echo "/flow:release \"$REQ_ID\""
             ;;
-        quality|qa)
-            echo "/flow-quality \"$REQ_ID\""
-            echo "/flow-release \"$REQ_ID\""
+        verify)
+            echo "/flow:verify \"$REQ_ID\" --strict"
+            echo "/flow:release \"$REQ_ID\""
             ;;
         release)
-            echo "/flow-release \"$REQ_ID\""
+            echo "/flow:release \"$REQ_ID\""
             ;;
     esac
 

package/.claude/scripts/run-quality-gates.sh

@@ -25,7 +25,7 @@ Usage: run-quality-gates.sh <phase> [--json] [--verbose]
 Execute quality gate verification commands for a phase.
 
 Arguments:
-    phase       Phase name (flow-dev, flow-review, flow-quality, flow-qa, flow-release)
+    phase       Phase name (flow-dev, flow-review, flow-quality, flow-release)
 
 Options:
     --json      Output results as JSON

package/.claude/scripts/setup-epic.sh

@@ -78,7 +78,7 @@ validate_req_id "$REQ_ID" || exit 1
 # Ensure the requirement directory exists
 if [[ ! -d "$REQ_DIR" ]]; then
     echo "ERROR: Requirement directory not found: $REQ_DIR" >&2
-    echo "Run /flow-init first to create the requirement structure." >&2
+    echo "Run /flow:init first to create the requirement structure." >&2
     exit 1
 fi
 
@@ -170,4 +170,4 @@ else
     echo "PRD_FILE: $PRD_FILE"
     echo "EPIC_FILE: $EPIC_FILE"
     echo "TASKS_FILE: $TASKS_FILE"
-fi
+fi

package/.claude/scripts/setup-ralph-loop.sh

@@ -91,14 +91,14 @@ fi
 REQ_DIR="devflow/requirements/${REQ_ID}"
 if [[ ! -d "$REQ_DIR" ]]; then
   echo "❌ Error: Requirement directory not found: $REQ_DIR" >&2
-  echo "   Run /flow-init first to create the requirement structure" >&2
+  echo "   Run /flow:init first to create the requirement structure" >&2
   exit 1
 fi
 
 # Check if TASKS.md exists
 if [[ ! -f "${REQ_DIR}/TASKS.md" ]]; then
   echo "❌ Error: TASKS.md not found in $REQ_DIR" >&2
-  echo "   Run /flow-epic first to generate tasks" >&2
+  echo "   Run /flow:spec first to generate tasks" >&2
   exit 1
 fi
 

package/.claude/scripts/validate-research.sh

@@ -303,7 +303,7 @@ main() {
   echo "════════════════════════════════════════════════════════════════════════"
   if [[ $total_errors -eq 0 ]]; then
     echo "✅ ALL VALIDATIONS PASSED"
-    echo "research.md is ready for /flow-prd"
+    echo "research.md is ready for /flow:spec"
     echo "════════════════════════════════════════════════════════════════════════"
     return 0
   else

package/.claude/scripts/verify-setup.sh

@@ -31,7 +31,7 @@ require_file() {
 require_dir "$CLAUDE_DIR/commands"
 require_dir "$CLAUDE_DIR/skills"
 require_dir "$CLAUDE_DIR/scripts"
-require_file "$CLAUDE_DIR/commands/flow-new.md"
+require_file "$CLAUDE_DIR/commands/flow/new.md"
 require_file "$CLAUDE_DIR/skills/cc-devflow-orchestrator/SKILL.md"
 
 echo "cc-devflow setup OK."

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