cc-devflow 2.4.6 → 4.1.0

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

@@ -13,267 +13,152 @@ Guide users to the correct agent/command WITHOUT duplicating their detailed stan
 ### 🏢 项目级工作流（Project-Level, 项目初期执行一次）
 
 ```
-/core-roadmap → ROADMAP.md + BACKLOG.md (产品路线图)
-/core-architecture → ARCHITECTURE.md (系统架构设计)
-/core-guidelines → frontend-guidelines.md / backend-guidelines.md (项目规范)
-/core-style → STYLE.md (设计风格指南) 
+/core:roadmap → ROADMAP.md + BACKLOG.md (产品路线图)
+/core:architecture → ARCHITECTURE.md (系统架构设计)
+/core:guidelines → frontend-guidelines.md / backend-guidelines.md (项目规范)
+/core:style → STYLE.md (设计风格指南)
 ```
 
 ### 📦 需求级工作流（Requirement-Level, 每个需求执行一次）
 
 ```
-/flow-init → research.md + tasks.json + BRAINSTORM.md (研究初始化 + 头脑风暴)
+/flow:init → research.md + tasks.json + BRAINSTORM.md (研究初始化 + 头脑风暴)
      ↓
-/flow-clarify → clarifications/*.md (11 维度歧义扫描, 可选)
+/flow:clarify → clarifications/*.md (11 维度歧义扫描, 可选)
      ↓
-/flow-prd → PRD.md (invoke prd-writer agent, 需 BRAINSTORM.md 对齐)
+/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-checklist → checklists/*.md (需求质量检查, 可选)
+/flow:dev → TASKS.md execution (TDD + Autonomous mode default)
      ↓
-/flow-tech → TECH_DESIGN.md + data-model + contracts (invoke tech-architect agent)
+/flow:quality → Quality verification
      ↓
-/flow-ui → UI_PROTOTYPE.html (invoke ui-designer agent, 可选, 引用 STYLE.md)
+/flow:release → PR creation + deployment
      ↓
-/flow-epic → EPIC.md + TASKS.md (invoke planner, bite-sized tasks)
-     ↓
-/flow-dev → TASKS.md execution (TDD + Autonomous mode default)
-     ↓
-/flow-review → SPEC_REVIEW.md + CODE_QUALITY_REVIEW.md (Two-Stage Review) 
-     ↓
-/flow-qa → QA reports (invoke qa-tester + security-reviewer agents)
-     ↓
-/flow-release → PR creation + deployment (分支完成决策)
-     ↓
-/flow-verify → consistency check (invoke consistency-checker agent, 任意阶段可调用)
+/flow:verify → consistency check (任意阶段可调用)
+```
+
+### 🚀 简化流程
+
+```
+【精简流程】(适合小需求, 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
+
+【完整流程】(适合大需求, 5 步)
+/flow:init → /flow:clarify → /flow:spec → /flow:dev → /flow:quality --full → /flow:release
 ```
 
 ### 🐛 Bug 修复工作流
 
 ```
-/flow-fix "BUG-123|描述" → 系统化调试 (4阶段: Root Cause → Pattern → Hypothesis → TDD Fix)
+/flow:fix "BUG-123|描述" → 系统化调试 (4阶段: Root Cause → Pattern → Hypothesis → TDD Fix)
 ```
 
 **说明**:
-- 项目级命令建立全局标准（SSOT），需求级命令引用这些标准
-- `/flow-init` 包含 Brainstorming 阶段，生成 BRAINSTORM.md 作为需求「北极星」
-- `/flow-prd` 需要 BRAINSTORM.md 对齐检查
-- `/flow-clarify` 在 PRD 前可选执行，消除 research.md 中的歧义
-- `/flow-epic` 使用 bite-sized tasks 原则 (2-5分钟/任务)
-- `/flow-dev` 默认 Autonomous 模式（自动重试），使用 `--manual` 退出到 Manual 模式 
-- `/flow-review` 是新增的两阶段审查 (Spec Compliance → Code Quality)
-- `/flow-ui` 和 `/flow-dev` 自动加载 `devflow/STYLE.md`（如存在）
-- 项目级命令可按需执行，无严格顺序要求
+- `/flow:spec` 是统一规格命令，合并 PRD/Tech/UI/Epic 为单一命令
+- `/flow:spec` 内部并行执行 Tech + UI，减少 ~35% 设计阶段时间
+- `/flow:dev` 默认 Autonomous 模式（自动重试），使用 `--manual` 退出到 Manual 模式
 
 ## Agent Delegation 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)
+
 ### When User Asks About Requirements Clarification
-- **DO**: Recommend `/flow-clarify` command → invokes clarify-analyst agent
-- **DON'T**: Duplicate clarification logic (flow-clarify.md has ~128 lines)
-- **Link**: See [.claude/commands/flow-clarify.md](.claude/commands/flow-clarify.md) for details
-- **Outputs**: clarifications/[timestamp]-flow-clarify.md (澄清报告)
-- **Features**: 11-dimension scan, ≤5 prioritized questions, session recovery
-
-### When User Asks About PRD
-- **DO**: Recommend `/flow-prd` command → invokes prd-writer agent
-- **DON'T**: Duplicate PRD standards (prd-writer agent has ~300 lines)
-- **Link**: See [.claude/agents/prd-writer.md](.claude/agents/prd-writer.md) for PRD details
-- **Standards**: INVEST principles, Anti-Expansion mandate, Given-When-Then criteria
-
-### When User Asks About Requirement Quality Checklist
-- **DO**: Recommend `/flow-checklist` command → invokes checklist-agent
-- **DON'T**: Duplicate checklist standards (checklist-agent has ~180 lines)
-- **Link**: See [.claude/commands/flow-checklist.md](.claude/commands/flow-checklist.md) for details
-- **Outputs**: checklists/*.md (ux, api, security, performance, data, general)
-- **Features**: 5 quality dimensions, Anti-Example rules, 80% gate threshold
-- **Level**: Requirement-level (optional, before /flow-epic)
-
-### When User Asks About Tech Design
-- **DO**: Recommend `/flow-tech` command → invokes tech-architect agent
-- **DON'T**: Duplicate tech standards (tech-architect agent has ~516 lines)
-- **Link**: See [.claude/agents/tech-architect.md](.claude/agents/tech-architect.md) for design details
-- **Outputs**: TECH_DESIGN.md, data-model.md, contracts/, quickstart.md
-
-### When User Asks About Design Style Guide
-- **DO**: Recommend `/core-style` command → invokes style-guide-generator agent
-- **DON'T**: Duplicate style guide standards (style-guide-generator agent has ~400 lines)
-- **Link**: See [.claude/agents/style-guide-generator.md](.claude/agents/style-guide-generator.md) for details
-- **Outputs**: STYLE.md (project-level SSOT for visual consistency)
-- **Level**: Project-level (execute once per project)
-
-### When User Asks About UI Prototype
-- **DO**: Recommend `/flow-ui` command → invokes ui-designer agent
-- **DON'T**: Duplicate UI standards (ui-designer agent has ~485 lines)
-- **Link**: See [.claude/agents/ui-designer.md](.claude/agents/ui-designer.md) for UI details
-- **Features**: 80+ design masters sampling, responsive design, NO PLACEHOLDER, references STYLE.md
-
-### When User Asks About Task Planning
-- **DO**: Recommend `/flow-epic` command → invokes planner agent
-- **DON'T**: Duplicate planning logic (planner agent has ~400 lines)
-- **Link**: See [.claude/agents/planner.md](.claude/agents/planner.md) for task breakdown rules
-- **Enforces**: Phase -1 Gates (Articles VII, VIII, IX), TDD sequence
+- **DO**: Recommend `/flow:clarify` command → invokes clarify-analyst agent
+- **Link**: See `.claude/commands/flow/clarify.md` for details
+
+### 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
 
 ### When User Asks About QA/Security
-- **DO**: Recommend `/flow-qa` command → invokes qa-tester + security-reviewer agents
-- **DON'T**: Duplicate QA standards (qa-tester agent has ~300 lines)
-- **Link**: See [.claude/agents/qa-tester.md](.claude/agents/qa-tester.md) for QA details
+- **DO**: Recommend `/flow:quality` command → invokes qa-tester + security-reviewer agents
+- **Link**: See `.claude/agents/qa-tester.md` for QA details
 
-### When User Asks About Code Review (v2.1.0 新增)
-- **DO**: Recommend `/flow-review` command → invokes spec-reviewer + code-quality-reviewer agents
-- **DON'T**: Duplicate review standards (Two-Stage Review)
-- **Link**: See [.claude/commands/flow-review.md](.claude/commands/flow-review.md) for details
-- **Features**: Stage 1 (Spec Compliance) → Stage 2 (Code Quality), 不信任实现者报告
+### 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
 
-### When User Asks About Bug Fix (v2.1.0 新增)
-- **DO**: Recommend `/flow-fix` command → 4-phase systematic debugging
-- **DON'T**: Guess and fix without investigation
-- **Link**: See [.claude/commands/flow-fix.md](.claude/commands/flow-fix.md) for details
-- **Features**: Root Cause → Pattern → Hypothesis → TDD Fix, Iron Law enforcement
+### When User Asks About Bug Fix
+- **DO**: Recommend `/flow:fix` command → 4-phase systematic debugging
+- **Link**: See `.claude/commands/flow/fix.md` for details
 
-## Phase Gates (Quick Reference Only)
+## Phase Gates (Quick Reference)
 
 ### Entry Gates
-- **flow-init Entry**: Git 工作区干净, main 分支
-- **flow-clarify Entry**: research.md 存在, phase0_complete == true
-- **flow-prd Entry**: BRAINSTORM.md 存在, research.md 无 TODO placeholder 
-- **flow-checklist Entry**: PRD.md 必须完成 (prd_complete == true)
-- **flow-tech Entry**: PRD.md 必须完成
-- **flow-ui Entry**: PRD.md 必须完成（可与 tech 并行）
-- **flow-epic Entry**: PRD 完成，tech/ui 推荐但可选，Checklist Gate (如存在 checklists/)
-- **flow-dev Entry**: EPIC.md + TASKS.md 存在
-- **flow-review Entry**: development_complete == true 
-- **flow-qa Entry**: review_complete == true (或 development_complete)
-- **flow-release Entry**: qa_complete == true
+- **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
 
 ### Exit Gates
-- **flow-init Exit**: research.md 5-level quality check, BRAINSTORM.md 完整
-- **flow-clarify Exit**: clarification report 完整, orchestration_status.clarify_complete == true
-- **flow-prd Exit**: PRD.md 无 placeholder, Constitution 合规, BRAINSTORM 对齐
-- **flow-tech Exit**: TECH_DESIGN.md + data-model + contracts 完整
-- **flow-epic Exit**: TASKS.md TDD 顺序正确, bite-sized tasks, Phase -1 Gates 通过
-- **flow-dev Exit**: 所有 TASKS 完成, TDD Checkpoint 通过, 测试通过
-- **flow-review Exit**: SPEC_REVIEW.md + CODE_QUALITY_REVIEW.md 均 PASS 
-- **flow-qa Exit**: 无 high-severity 漏洞
-- **flow-release Exit**: PR 创建成功, 分支决策完成 
-
-**For Details**: See [orchestration_status.json](devflow/requirements/REQ-XXX/orchestration_status.json) and [EXECUTION_LOG.md](devflow/requirements/REQ-XXX/EXECUTION_LOG.md)
+- **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 创建成功
 
 ## State Machine: Status → Recommended Command
 
-Read `orchestration_status.json` to determine current phase:
-
 ```yaml
 status: "initialized"
-  → Recommend: /flow-clarify (optional, clarify ambiguities)
-  → Alternative: /flow-prd (skip clarification, generate PRD directly)
-  → Note: BRAINSTORM.md 已在 /flow-init 生成 
+  → Recommend: /flow:spec (统一规格阶段)
+  → Alternative: /flow:clarify (optional)
 
 status: "clarify_complete" OR "clarify_skipped"
-  → Recommend: /flow-prd (generate PRD)
+  → Recommend: /flow:spec
 
-status: "prd_complete"
-  → Recommend: /flow-tech (generate technical design)
-  → Alternative: /flow-ui (generate UI prototype, optional)
-
-status: "tech_design_complete"
-  → If UI not done: /flow-ui (optional)
-  → Else: /flow-epic (generate EPIC and TASKS)
-
-status: "epic_complete"
-  → Recommend: /flow-dev (TDD development, Autonomous mode default)
-  → Alternative: /flow-dev --manual (Manual mode for complex requirements) 
+status: "spec_complete"
+  → Recommend: /flow:dev (TDD development, Autonomous mode default)
 
 status: "development_complete"
-  → Recommend: /flow-review (Two-Stage Code Review) 
-  → Alternative: /flow-qa (skip review, go directly to QA)
+  → Recommend: /flow:quality
 
-status: "review_complete"
-  → Recommend: /flow-qa (quality assurance and security review)
-
-status: "qa_complete"
-  → Recommend: /flow-release (create PR and release)
+status: "quality_complete"
+  → Recommend: /flow:release
 
 status: "released"
-  → Recommend: /flow-verify (final consistency check)
+  → Recommend: /flow:verify (final consistency check)
 ```
 
-## Troubleshooting Quick Routing
-
-### Phase gate blocked?
-- **Action**: Check `orchestration_status.json` for current status
-- **Script**: Run `.claude/scripts/check-prerequisites.sh --json`
-
-### Document missing?
-- **Action**: Check which phase is incomplete
-- **Script**: Run `.claude/scripts/generate-status-report.sh`
-
-### Need detailed standards?
-- **Clarify**: See flow-clarify.md command + clarify-analyst agent
-- **PRD**: Consult prd-writer agent
-- **Tech**: Consult tech-architect agent
-- **UI**: Consult ui-designer agent
-- **Tasks**: Consult planner agent
-- **QA**: Consult qa-tester agent
-
-### Constitution violation?
-- **Real-time check**: constitution-guardian guardrail (PreToolUse hook)
-- **Batch validation**: Run `.claude/scripts/validate-constitution.sh`
-- **Reference**: See `.claude/rules/project-constitution.md` 
-- **Rationalization Library**: See `.claude/rules/rationalization-library.md` 
-
-### TDD order violated?
-- **Real-time check**: devflow-tdd-enforcer guardrail (PreToolUse hook)
-- **Manual check**: See TASKS.md, tests MUST be marked [x] before implementation
-- **TDD Skill**: See `.claude/skills/flow-tdd/SKILL.md` 
-
 ## Auxiliary Commands
 
 ### Status and Progress
-- `/flow-status` - Query requirement progress
-- `/flow-update "REQ-123" "T012"` - Update task completion
-- `/flow-restart "REQ-123" --from=epic` - Resume interrupted workflow
+- `/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
+- `/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 修复 (4阶段调试法)
-- `/problem-analyzer "<issue>"` - Problem diagnosis
+- `/flow:fix "BUG-123|描述"` - 系统化 BUG 修复
+- `/util:problem-analyzer "<issue>"` - Problem diagnosis
 
 ### Code Review
-- `/flow-review "REQ-123"` - Two-Stage Code Review (Spec → Quality)
-- `/code-review-high "<diff>"` - High-rigor code review
-
-## Integration with Other Skills
-
-### Guardrails (实时阻断)
-- **devflow-tdd-enforcer**: Enforces TDD order in TASKS.md
-- **constitution-guardian**: Enforces Constitution compliance
-
-### Workflow Skills
-- **flow-brainstorming**: 需求头脑风暴，生成 BRAINSTORM.md
-- **flow-tdd**: TDD Iron Law 执行
-- **flow-debugging**: 4阶段系统化调试
-- **flow-receiving-review**: 处理代码审查反馈
-- **flow-finishing-branch**: 分支完成决策
-- **verification-before-completion**: 验证闸门
-
-### Reference Skills
-- **devflow-file-standards**: File naming and directory structure reference
-- **devflow-constitution-quick-ref**: Constitution quick reference
+- `/flow:review "REQ-123"` - Two-Stage Code Review
+- `/util:code-review "<diff>"` - High-rigor code review
 
 ## Design Principle
 
-**This skill does NOT contain**:
-- ❌ Detailed agent execution standards (those are in agent files)
-- ❌ Full Phase Gate validation logic (those are in flow command files)
-- ❌ Complete Constitution articles (those are in project-constitution.md)
-
 **This skill ONLY contains**:
 - ✅ Workflow routing (which command to run next)
 - ✅ Agent delegation (which agent handles what)
-- ✅ Quick reference (Phase Gates summary, not full details)
+- ✅ Quick reference (Phase Gates summary)
 - ✅ Links to detailed documentation
 
-**Rationale**: Avoid duplication ("不重不漏" principle). Agents and Commands own detailed standards.
+**Rationale**: Avoid duplication. Agents and Commands own detailed standards.

package/.claude/skills/domain/using-git-worktrees/SKILL.md

@@ -0,0 +1,252 @@
+---
+name: using-git-worktrees
+description: 'Git Worktree management for parallel development. Enables multiple Claude Code sessions working on different requirements simultaneously.'
+---
+
+# Using Git Worktrees Skill
+
+> [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
+
+## Purpose
+
+支持多需求并行开发，每个 worktree 独立的 Claude 会话，互不干扰。
+
+## When to Use
+
+- 多需求并行开发
+- 代码审查时需要隔离环境
+- 紧急修复时不丢失当前工作
+- 需要在不同分支间快速切换
+
+## Core Concepts
+
+### Worktree vs Branch
+
+| 传统分支 | Git Worktree |
+|---------|--------------|
+| `git checkout` 切换 | `cd` 切换目录 |
+| 需要 stash 当前工作 | 工作区完全隔离 |
+| 单一 Claude 会话 | 每个 worktree 独立会话 |
+| 切换耗时 ~30s | 切换耗时 ~1s |
+
+### Directory Layout
+
+```
+~/projects/
+├── cc-devflow/                    # 主仓库 (main 分支)
+├── cc-devflow-REQ-001/            # REQ-001 worktree
+├── cc-devflow-REQ-002/            # REQ-002 worktree
+├── cc-devflow-analysis/           # 只读分析 worktree (可选)
+└── cc-devflow-hotfix/             # 紧急修复 worktree (可选)
+```
+
+### Naming Convention
+
+```
+Worktree 目录: {repo-name}-{REQ_ID}
+对应分支: feature/{REQ_ID}-{slug}
+```
+
+## Commands
+
+### Create Worktree
+
+```bash
+# 创建新 worktree + 分支
+bash scripts/worktree-create.sh "REQ-123" "Feature Title"
+
+# 仅创建 worktree (分支已存在)
+bash scripts/worktree-create.sh "REQ-123" --existing-branch
+```
+
+### List Worktrees
+
+```bash
+# 列出所有 worktree
+bash scripts/worktree-list.sh
+
+# JSON 格式输出
+bash scripts/worktree-list.sh --json
+```
+
+### Switch Worktree
+
+```bash
+# 切换到指定 worktree
+bash scripts/worktree-switch.sh "REQ-123"
+
+# 或直接 cd
+cd ../cc-devflow-REQ-123
+```
+
+### Cleanup Worktree
+
+```bash
+# 清理单个 worktree
+bash scripts/worktree-cleanup.sh "REQ-123"
+
+# 清理所有已合并的 worktree
+bash scripts/worktree-cleanup.sh --merged
+```
+
+### Status Check
+
+```bash
+# 检查当前 worktree 状态
+bash scripts/worktree-status.sh
+```
+
+## Shell Aliases (Recommended)
+
+将以下内容添加到 `~/.zshrc` 或 `~/.bashrc`:
+
+```bash
+# 快速导航
+alias za='cd $(git rev-parse --show-toplevel 2>/dev/null || echo .)'  # 当前 worktree 根目录
+alias zl='git worktree list'                                           # 列出所有 worktree
+alias zm='cd ~/projects/cc-devflow'                                    # 主仓库
+
+# 快速切换函数
+zw() {
+  local req_id="${1:-}"
+  if [[ -z "$req_id" ]]; then
+    echo "Usage: zw REQ-123"
+    return 1
+  fi
+  local repo_name=$(basename $(git -C ~/projects/cc-devflow rev-parse --show-toplevel 2>/dev/null))
+  local target_dir=~/projects/${repo_name}-${req_id}
+  if [[ -d "$target_dir" ]]; then
+    cd "$target_dir"
+  else
+    echo "Worktree not found: $target_dir"
+    return 1
+  fi
+}
+```
+
+## Integration with CC-DevFlow
+
+### flow-init
+
+默认使用 worktree 模式:
+
+```bash
+/flow-init "REQ-123|Feature Title"
+# 创建: ../cc-devflow-REQ-123/
+# 分支: feature/REQ-123-feature-title
+```
+
+兼容模式 (传统分支):
+
+```bash
+/flow-init "REQ-123|Feature Title" --branch-only
+```
+
+### flow-release
+
+自动清理 worktree:
+
+```bash
+/flow-release "REQ-123"
+# 1. 合并分支
+# 2. 删除 worktree
+# 3. 删除分支
+```
+
+### flow-restart
+
+切换到已有 worktree:
+
+```bash
+/flow-restart "REQ-123"
+# cd ../cc-devflow-REQ-123
+```
+
+## Session Management
+
+每个 worktree 可以运行独立的 Claude Code 会话:
+
+```bash
+# 终端 1: REQ-001
+cd ~/projects/cc-devflow-REQ-001
+claude
+
+# 终端 2: REQ-002
+cd ~/projects/cc-devflow-REQ-002
+claude
+
+# 终端 3: 主仓库 (代码审查)
+cd ~/projects/cc-devflow
+claude
+```
+
+## Best Practices
+
+### 1. 保持主仓库干净
+
+主仓库 (`cc-devflow/`) 应始终在 `main` 分支，用于:
+- 创建新 worktree
+- 代码审查
+- 合并操作
+
+### 2. 定期清理
+
+```bash
+# 清理已合并的 worktree
+bash scripts/worktree-cleanup.sh --merged
+```
+
+### 3. 命名一致性
+
+- Worktree 目录: `{repo}-{REQ_ID}`
+- 分支名: `feature/{REQ_ID}-{slug}`
+
+### 4. 紧急修复流程
+
+```bash
+# 1. 在主仓库创建 hotfix worktree
+cd ~/projects/cc-devflow
+git worktree add ../cc-devflow-hotfix -b hotfix/critical-fix
+
+# 2. 修复并合并
+cd ../cc-devflow-hotfix
+# ... 修复代码 ...
+git push origin hotfix/critical-fix
+
+# 3. 清理
+cd ~/projects/cc-devflow
+git worktree remove ../cc-devflow-hotfix
+git branch -d hotfix/critical-fix
+```
+
+## Error Handling
+
+| 错误 | 解决方案 |
+|------|----------|
+| Worktree 目录已存在 | 使用 `--force` 或手动删除 |
+| 分支已被其他 worktree 使用 | 先删除旧 worktree |
+| 主仓库不在 main 分支 | `git checkout main` |
+| 磁盘空间不足 | 清理已合并的 worktree |
+
+## Scripts Reference
+
+| Script | Purpose |
+|--------|---------|
+| `scripts/worktree-create.sh` | 创建 worktree |
+| `scripts/worktree-list.sh` | 列出 worktree |
+| `scripts/worktree-switch.sh` | 切换 worktree |
+| `scripts/worktree-cleanup.sh` | 清理 worktree |
+| `scripts/worktree-status.sh` | 状态检查 |
+
+## Assets Reference
+
+| Asset | Purpose |
+|-------|---------|
+| `assets/SHELL_ALIASES.md` | Shell 别名模板 |
+
+---
+
+**Related Skills**:
+- `flow-init` - 需求初始化 (worktree 创建)
+- `flow-release` - 发布管理 (worktree 清理)
+- `finishing-branch` - 分支完成决策