cc-devflow 4.3.0 → 4.4.1

package/.claude/docs/templates/INIT_FLOW_TEMPLATE.md

@@ -1,198 +0,0 @@
-# Flow-Init Execution Flow Template
-
-> Detailed stages for `/flow:init` requirement initialization
-
-<!-- ============================================================
-     调用上下文声明 (Invocation Context Declaration)
-     ============================================================
-
-本模板由 `/flow:init` 命令通过 {TEMPLATE:flow} 引用加载。
-
-模板中的 {SCRIPT:xxx} 占位符引用 flow-init.md 头文件中的 scripts 定义：
-```yaml
-# 来源: .claude/commands/flow/init.md 头文件
-scripts:
-  create: .claude/scripts/create-requirement.sh
-  prereq: .claude/scripts/check-prerequisites.sh
-  research_tasks: .claude/scripts/generate-research-tasks.sh
-  populate_tasks: .claude/scripts/populate-research-tasks.sh
-  consolidate: .claude/scripts/consolidate-research.sh
-  validate_research: .claude/scripts/validate-research.sh
-```
-
-占位符解析:
-- {SCRIPT:prereq}           → bash .claude/scripts/check-prerequisites.sh
-- {SCRIPT:create}           → bash .claude/scripts/create-requirement.sh
-- {SCRIPT:research_tasks}   → bash .claude/scripts/generate-research-tasks.sh
-- {SCRIPT:populate_tasks}   → bash .claude/scripts/populate-research-tasks.sh
-- {SCRIPT:consolidate}      → bash .claude/scripts/consolidate-research.sh
-- {SCRIPT:validate_research} → bash .claude/scripts/validate-research.sh
-============================================================ -->
-
----
-
-## Stage 1: Entry Gate (参数验证)
-
-```bash
-# 1. 解析参数
-REQ_ID|TITLE|PLAN_URLS → 验证 REQ_ID 格式: ^(REQ|BUG)-[0-9]+$
-→ 若 TITLE 含中文/非ASCII，使用模型意译生成 BRANCH_TITLE_EN（英文语义翻译，禁止拼音/音译）
-→ BRANCH_TITLE_EN 仅用于分支名，文档标题仍使用原始 TITLE
-→ 若意译不确定或未生成 ASCII 结果，向用户确认英文分支标题
-
-# 2. 前置条件检查
-bash {SCRIPT:prereq} --json --paths-only
-→ Git 状态干净 + devflow/ 目录存在
-
-# 3. 目录唯一性检查
-→ 确认 devflow/requirements/${REQ_ID}/ 不存在
-```
-
----
-
-## Stage 1.2: Git Branch Creation
-
-```bash
-# 创建功能分支
-Requirements: feature/${REQ_ID}-${slug(BRANCH_TITLE_EN)}
-Bug Fixes:    bugfix/${BUG_ID}-${slug(BRANCH_TITLE_EN)}
-
-# BRANCH_TITLE_EN = TITLE 的英文意译 (语义为准，非拼音，使用模型意译)
-# slug() = lowercase, replace spaces/special chars with hyphens
-```
-
----
-
-## Stage 1.5: Context Loading (路线图与架构)
-
-**目标**: 理解需求在项目中的位置
-
-```bash
-# 检查 ROADMAP.md 和 ARCHITECTURE.md
-→ 如果存在: 加载上下文，展示需求位置
-→ 如果不存在: 提示可选运行 /core-roadmap (不阻塞执行)
-```
-
----
-
-## Stage 2: Directory Initialization
-
-```bash
-# 创建需求目录
-bash {SCRIPT:create} "${REQ_ID}" --title "${TITLE}" --branch-title "${BRANCH_TITLE_EN}" --json
-
-→ 若未生成 BRANCH_TITLE_EN，则省略 --branch-title
-
-# 生成文件
-devflow/requirements/${REQ_ID}/
-├── README.md
-├── EXECUTION_LOG.md
-├── orchestration_status.json
-└── research/ (空目录)
-```
-
----
-
-## Stage 2.5: Research (Subagent Mandatory)
-
-**目标**: 研究默认必跑，但研究过程必须“隔离上下文”。
-
-**规则**: 大内容写入 `research/`，主会话只保留路径引用与决策摘要。
-
-### Mandatory: Call `flow-researcher` Subagent
-
-```
-Task tool call:
-  subagent_type: "flow-researcher"
-  prompt: (JSON) reqId/reqDir/title/planUrls/contextFiles
-```
-
-**产物** (由 subagent 写入):
-- `research/internal/codebase-overview.md`
-- `research/mcp/$(date +%Y%m%d)/**`
-- `research/research-summary.md`
-- `research/tasks.json`
-- `research/research.md`
-
----
-
-## Stage 2.6: Research Consolidation
-
-> 该阶段由 `flow-researcher` subagent 执行（含 tasks 生成/回填/整合/校验）。
-
----
-
-
-
-## Stage 3: README Generation
-
-```bash
-# 生成工作流指南
-→ devflow/requirements/${REQ_ID}/README.md
-→ 包含: 需求概述、工作流步骤、检查清单
-```
-
----
-
-## Stage 4: Exit Gate (5-Level Quality Check)
-
-### Level 1: File Existence Check
-```bash
-→ 验证所有必需文件已创建
-```
-
-### Level 2: Research.md Structure Validation
-```bash
-bash {SCRIPT:validate_research} "${REQ_DIR}" --strict
-→ 检查 research.md 结构
-```
-
-### Level 3: Research.md Content Quality
-```bash
-→ 无 TODO/FIXME/{{PLACEHOLDER}} 标记
-→ 每个 Decision block 完整
-```
-
-### Level 4: Research Tasks Validation
-```bash
-→ 验证 tasks.json 格式和内容
-```
-
-### Level 5: Git & Status & Constitution
-```bash
-→ Git 分支创建成功
-→ orchestration_status.json 正确
-→ Constitution 符合性检查
-```
-
----
-
-## Output Structure
-
-```
-devflow/requirements/${REQ_ID}/
-├── README.md
-├── research/
-│   ├── internal/
-│   │   └── codebase-overview.md
-│   ├── mcp/
-│   │   └── $(date +%Y%m%d)/
-│   │       ├── official/
-│   │       ├── guides/
-│   │       ├── tutorials/
-│   │       └── examples/
-│   ├── research.md
-│   ├── research-summary.md
-│   └── tasks.json
-├── EXECUTION_LOG.md
-└── orchestration_status.json
-```
-
-**Git**:
-- Branch: `feature/${REQ_ID}-${slug(BRANCH_TITLE_EN)}`
-- Status: orchestration_status.json.status = "initialized"
-- Phase: orchestration_status.json.phase = "planning"
-
----
-
-**Last Updated**: 2025-12-19

package/.claude/docs/templates/INTENT_CLARIFICATION_TEMPLATE.md

@@ -1,57 +0,0 @@
-# Requirement Clarification for {{INTENT_SUMMARY}}
-
-> **Session ID**: {{SESSION_ID}}
-> **Timestamp**: {{TIMESTAMP}}
-> **Round**: {{CLARIFICATION_ROUND}}/{{MAX_ROUNDS}}
-
----
-
-## Current Understanding:
-
-### 📊 Analysis Summary
-- **Domain**: {{IDENTIFIED_DOMAIN}}
-- **Target Users**: {{TARGET_USERS}}
-- **Core Function**: {{MAIN_PURPOSE}}
-- **Complexity**: {{COMPLEXITY_LEVEL}}
-- **Confidence**: {{CONFIDENCE_PERCENTAGE}}%
-
-### 🎯 Key Information Collected
-{{COLLECTED_INFORMATION}}
-
-### ❓ Information Gaps
-{{MISSING_INFORMATION}}
-
----
-
-## Critical Questions (Please answer to proceed):
-
-{{#QUESTIONS}}
-### {{QUESTION_NUMBER}}. {{QUESTION_TEXT}}
-
-**Why this matters**: {{EXPLANATION}}
-
-**Examples**: {{HELPFUL_EXAMPLES}}
-
-**Your answer**: _[Please provide your response here]_
-
----
-{{/QUESTIONS}}
-
-## Next Steps:
-
-{{NEXT_ACTION_DESCRIPTION}}
-
-### Progress Indicator:
-```text
-[{{PROGRESS_BAR}}] {{PROGRESS_PERCENTAGE}}% complete
-```
-
-### Estimated Information Completeness:
-- ✅ **Core Definition**: {{CORE_COMPLETENESS}}%
-- {{#FUNCTIONAL_SCOPE_STATUS}}{{FUNCTIONAL_SCOPE_STATUS}}{{/FUNCTIONAL_SCOPE_STATUS}} **Functional Scope**: {{FUNCTIONAL_COMPLETENESS}}%
-- {{#TECHNICAL_CONTEXT_STATUS}}{{TECHNICAL_CONTEXT_STATUS}}{{/TECHNICAL_CONTEXT_STATUS}} **Technical Context**: {{TECHNICAL_COMPLETENESS}}%
-- {{#VALIDATION_STATUS}}{{VALIDATION_STATUS}}{{/VALIDATION_STATUS}} **Validation Criteria**: {{VALIDATION_COMPLETENESS}}%
-
----
-
-**Tip**: The more specific your answers, the better I can help create a comprehensive PRD that meets your needs.

package/.claude/docs/templates/JOURNAL_TEMPLATE.md

@@ -1,75 +0,0 @@
----
-developer: "{DEVELOPER}"
-journal_number: 1
-created_at: "{TIMESTAMP}"
----
-
-# Developer Journal: {DEVELOPER}
-
-> **[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md
-
----
-
-## [{DATE} {TIME}] Session Start
-
-**REQ**: {REQ_ID}
-**Phase**: {PHASE}
-**Task**: {TASK_ID}
-
-### Context Recovery
-
-Previous session ended at:
-- Last completed task: {LAST_TASK}
-- Current blockers: {BLOCKERS}
-- Open questions: {QUESTIONS}
-
-### Session Goals
-
-1. Goal 1
-2. Goal 2
-
----
-
-## [{DATE} {TIME}] Progress Update
-
-### Completed
-
-- [x] Task description
-
-### In Progress
-
-- [ ] Current task
-
-### Blockers
-
-- None
-
-### Notes
-
-- Important observation
-- Decision made
-
----
-
-## [{DATE} {TIME}] Session End
-
-### Summary
-
-Brief summary of what was accomplished.
-
-### Handoff Notes
-
-For next session:
-- Continue with: {NEXT_TASK}
-- Watch out for: {WARNINGS}
-- Questions to resolve: {QUESTIONS}
-
----
-
-<!--
-Journal Guidelines:
-- Max 2000 lines per file
-- When approaching limit, create journal-{N+1}.md
-- Keep entries concise but informative
-- Focus on decisions and blockers, not routine progress
--->

package/.claude/docs/templates/NEW_ORCHESTRATION_TEMPLATE.md

@@ -1,76 +0,0 @@
-# Mainline Orchestration Template
-
-> Canonical execution flow for requirement delivery (`/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release`)
-
----
-
-## Stage Execution Skeleton
-
-### [1/5] /flow:init
-- 创建需求目录 + 运行时上下文
-- Exit Gate: `status in {initialized, context_packed}`
-
-### [2/5] /flow:spec
-- 统一规格阶段（PRD/Tech/UI/Task Manifest）
-- Exit Gate: `status = spec_complete` 或 `phase = planning`
-
-### [3/5] /flow:dev
-- 按 manifest 执行开发，支持 `--resume`
-- Exit Gate: `status in {development_complete, development_in_progress}`
-
-### [4/5] /flow:verify
-- 快速/严格质量闸
-- 严格模式输出 `report-card.json` 作为发布准入依据
-
-### [5/5] /flow:release
-- 读取 verify 结果并完成发布收口
-- 生成发布计划并清理运行时噪音
-
----
-
-## Progress Display Format
-
-```text
-🎯 CC-DevFlow 主链交付
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-需求: REQ-123 | 支持用户下单
-
-[1/5] ✅ 初始化完成
-[2/5] ✅ 规格完成
-[3/5] 🔄 开发执行中... (8/18 已完成)
-[4/5] ⏳ 等待质量闸...
-[5/5] ⏳ 等待发布...
-```
-
----
-
-## Output Structure
-
-```text
-devflow/requirements/${REQ_ID}/
-├── PRD.md
-├── TECH_DESIGN.md
-├── UI_PROTOTYPE.html            # 条件生成
-├── EPIC.md
-├── TASKS.md
-├── report-card.json             # /flow:verify 产物
-├── SECURITY_REPORT.md
-└── RELEASE_PLAN.md
-```
-
----
-
-## Status Tracking (Suggested)
-
-```json
-{
-  "status": "development_in_progress",
-  "phase": "development",
-  "initialized": true,
-  "spec_complete": true,
-  "development_complete": false,
-  "quality_complete": false,
-  "release_complete": false
-}
-```

package/.claude/docs/templates/PROPOSAL_TEMPLATE.md

@@ -1,91 +0,0 @@
-# proposal.md Template
-
-> **Purpose**: 需求提议模板，描述为什么需要和要做什么
-> **Location**: `devflow/requirements/${REQ_ID}/proposal.md`
-> **Version**: v4.3.0
-
----
-
-```markdown
----
-req_id: "${REQ_ID}"
-title: "${TITLE}"
-created_at: "${CREATED_AT}"
-status: "draft"
----
-
-# ${TITLE}
-
-## Why（为什么需要）
-
-[NEEDS CLARIFICATION: 为什么需要这个功能？解决什么问题？]
-
-### Background
-${背景描述}
-
-### Problem Statement
-${问题陈述}
-
-### Business Value
-${商业价值}
-
-## What（要做什么）
-
-[NEEDS CLARIFICATION: 具体要做什么？核心功能是什么？]
-
-### Core Features
-- ${核心功能 1}
-- ${核心功能 2}
-- ${核心功能 3}
-
-### Scope
-**In Scope**:
-- ${包含的功能}
-
-**Out of Scope**:
-- ${不包含的功能}
-
-### Success Criteria
-- ${成功标准 1}
-- ${成功标准 2}
-
-## References
-
-${如果有 PLAN_URLS，列在这里}
-- [External Doc 1](${URL})
-- [External Doc 2](${URL})
-
----
-
-## Constitutional Constraints
-
-- **Article X: Requirement Boundary** - 只实现明确请求的功能，不添加推测性特性
-- **Article I: Quality First** - 完整实现或不实现，禁止部分实现
-
-详见 `.claude/rules/project-constitution.md`
-```
-
----
-
-## Field Descriptions
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `req_id` | 需求 ID | "REQ-123" |
-| `title` | 需求标题 | "添加用户认证" |
-| `created_at` | 创建时间 (ISO 8601) | "2026-03-12T10:00:00Z" |
-| `status` | 状态 | "draft", "approved", "implemented" |
-
-## Why vs What
-
-- **Why**: 回答"为什么需要"，聚焦问题和价值
-- **What**: 回答"要做什么"，聚焦功能和范围
-
-## [NEEDS CLARIFICATION] 标记
-
-所有模糊点必须标记为 `[NEEDS CLARIFICATION: 具体问题]`，等待用户澄清。
-
----
-
-**Version**: v4.3.0
-**Related**: SPEC_TEMPLATE_DELTA.md（下一阶段生成）