cc-devflow 4.2.0 → 4.4.1

package/.claude/skills/utility/file-standards/SKILL.md

@@ -1,353 +0,0 @@
----
-name: devflow-file-standards
-description: File naming conventions, directory structure, and YAML frontmatter standards for CC-DevFlow. Consolidates shared conventions from all agents.
----
-
-# DevFlow File Standards
-
-## Purpose
-Consolidate file naming, directory structure, and format conventions that are shared across multiple agents and commands. This skill does NOT duplicate agent-specific standards.
-
-## Requirement IDs
-
-### Format
-```
-REQ-\d{3}    # e.g., REQ-001, REQ-042, REQ-123
-```
-
-### Usage
-- **Flow commands**: All `/flow-*` commands accept REQ-ID as argument
-- **Git branches**: `feature/REQ-XXX-{slug-title}`
-- **Directory paths**: `devflow/requirements/REQ-XXX/`
-- **Status tracking**: `orchestration_status.json` contains `reqId` field
-
-### Source
-- Enforced by: All 13 agents
-- Validated by: `.claude/scripts/check-prerequisites.sh`
-
-## Task IDs
-
-### Format
-```
-T\d{3}    # e.g., T001, T042, T123
-```
-
-### Usage in TASKS.md
-```markdown
-- [ ] **T001** [P] Task description
-- [ ] **T010** [US1] User story 1 task
-```
-
-### Labels
-- `[P]`: Parallel execution possible
-- `[US#]`: User story number (e.g., [US1], [US2])
-
-### Source
-- Generated by: planner agent
-- Format defined in: `.claude/docs/templates/TASKS_TEMPLATE.md`
-
-## Directory Structure
-
-### Requirements
-```
-devflow/requirements/REQ-XXX/
-├── research/                        # /flow-init 输出
-│   ├── research.md                  # consolidate-research.sh 生成
-│   ├── tasks.json                   # generate-research-tasks.sh 生成
-│   ├── internal/
-│   │   └── codebase-overview.md
-│   ├── mcp/                         # MCP 服务器调查（可选）
-│   └── codebase-tech-analysis.md   # /flow-tech 输出
-├── PRD.md                           # /flow-prd 输出 (prd-writer agent)
-├── TECH_DESIGN.md                   # /flow-tech 输出 (tech-architect agent)
-├── data-model.md                    # /flow-tech 输出 (extract-data-model.sh)
-├── contracts/                       # /flow-tech 输出 (export-contracts.sh)
-│   ├── api-users.yaml               # OpenAPI contracts
-│   └── api-auth.yaml
-├── quickstart.md                    # /flow-tech 输出 (generate-quickstart.sh)
-├── UI_PROTOTYPE.html                # /flow-ui 输出 (ui-designer agent, 可选)
-├── EPIC.md                          # /flow-epic 输出 (planner agent)
-├── TASKS.md                         # /flow-epic 输出 (planner agent)
-├── reviews/                         # /flow-qa 输出
-│   ├── TEST_PLAN.md                 # qa-tester agent
-│   ├── TEST_REPORT.md               # qa-tester agent
-│   └── SECURITY_REPORT.md           # security-reviewer agent
-├── EXECUTION_LOG.md                 # 事件日志 (所有 flow 命令追加)
-├── orchestration_status.json        # 状态跟踪 (所有 flow 命令更新)
-└── README.md                        # 工作流指南
-
-### Bugs
-```
-devflow/bugs/BUG-XXX/
-├── BUG_ANALYSIS.md                  # /flow-fix 输出 (bug-analyzer agent)
-├── PLAN.md                          # /flow-fix 输出 (planner agent)
-├── TASKS.md                         # /flow-fix 输出 (planner agent)
-├── EXECUTION_LOG.md
-└── status.json                      # 类似 orchestration_status.json
-```
-
-### Source
-- Created by: `.claude/scripts/create-requirement.sh`
-- Template: `.claude/docs/templates/` 目录
-- Enforced by: All flow commands
-
-## YAML Frontmatter
-
-### Document Types
-
-#### PRD.md
-```yaml
----
-reqId: REQ-123
-title: User Authentication
-version: 1.0.0
-createdAt: 2025-10-31T12:34:56Z
-updatedAt: 2025-10-31T15:20:30Z
-status: approved
-author: prd-writer agent
----
-```
-
-#### TECH_DESIGN.md
-```yaml
----
-reqId: REQ-123
-version: 1.0.0
-architecture: Microservices
-techStack:
-  - Node.js
-  - PostgreSQL
-  - Redis
-createdAt: 2025-10-31T14:10:00Z
-author: tech-architect agent
----
-```
-
-#### EPIC.md
-```yaml
----
-reqId: REQ-123
-title: User Authentication Epic
-version: 1.0.0
-estimatedEffort: 5 days
-createdAt: 2025-10-31T16:00:00Z
-author: planner agent
----
-```
-
-#### TASKS.md
-```yaml
----
-reqId: REQ-123
-totalTasks: 25
-completedTasks: 0
-version: 1.0.0
-createdAt: 2025-10-31T16:30:00Z
-updatedAt: 2025-10-31T16:30:00Z
-author: planner agent
----
-```
-
-### Source
-- Enforced by: prd-writer, tech-architect, planner agents
-- Parsed by: `.claude/scripts/check-prerequisites.sh`, `.claude/scripts/generate-status-report.sh`
-
-## orchestration_status.json
-
-### Structure (Requirements)
-```json
-{
-  "reqId": "REQ-123",
-  "title": "User Authentication",
-  "status": "initialized",
-  "phase": "planning",
-  "phase0_complete": false,
-  "phase1_complete": false,
-  "completedSteps": [],
-  "createdAt": "2025-10-31T12:34:56Z",
-  "updatedAt": "2025-10-31T12:34:56Z"
-}
-```
-
-### Status Values
-```
-initialized                → /flow-init 完成
-prd_generation_in_progress → /flow-prd 执行中
-prd_generation_failed      → /flow-prd 失败（可重试）
-prd_complete               → /flow-prd 完成
-
-tech_design_in_progress    → /flow-tech 执行中
-tech_design_failed         → /flow-tech 失败
-tech_design_complete       → /flow-tech 完成
-
-epic_generation_in_progress → /flow-epic 执行中
-epic_generation_failed      → /flow-epic 失败
-epic_complete               → /flow-epic 完成
-
-development_in_progress     → /flow-dev 执行中
-development_complete        → /flow-dev 完成
-
-qa_in_progress              → /flow-qa 执行中
-qa_complete                 → /flow-qa 完成
-
-released                    → /flow-release 完成
-```
-
-### Phase Values
-```
-planning       → 需求规划阶段 (init, prd)
-design         → 技术设计阶段 (tech, ui)
-epic_planning  → 任务规划阶段 (epic)
-implementation → 开发阶段 (dev)
-qa             → 质量保障阶段 (qa)
-release        → 发布阶段 (release)
-```
-
-### Source
-- Updated by: All flow commands
-- Read by: cc-devflow-orchestrator skill, check-prerequisites.sh
-- Schema: Implicitly defined across all flow command docs
-
-## status.json (for Bugs)
-
-### Structure
-```json
-{
-  "bugId": "BUG-456",
-  "title": "Fix login timeout",
-  "status": "initialized",
-  "phase": "analysis",
-  "severity": "high",
-  "createdAt": "2025-10-31T12:34:56Z",
-  "updatedAt": "2025-10-31T12:34:56Z"
-}
-```
-
-### Severity Values
-```
-critical  → 严重，系统不可用
-high      → 高，核心功能受影响
-medium    → 中，部分功能受影响
-low       → 低，轻微问题
-```
-
-### Source
-- Used by: `/flow-fix` command
-- Updated by: bug-analyzer agent
-
-## File Naming Patterns
-
-### Markdown Documents
-```
-UPPERCASE_WITH_UNDERSCORES.md    # Primary documents (PRD.md, EPIC.md, TASKS.md)
-lowercase-with-dashes.md         # Supporting documents (data-model.md, quickstart.md)
-```
-
-### Scripts
-```
-kebab-case.sh                    # All bash scripts (check-prerequisites.sh)
-kebab-case.ts                    # All TypeScript scripts (skill-activation-prompt.ts)
-```
-
-### Directories
-```
-lowercase                        # Top-level (devflow/, research/, contracts/)
-kebab-case                       # Multi-word (codebase-tech-analysis/)
-```
-
-### Source
-- Implicitly enforced by: All agents and scripts
-- No explicit validator
-
-## Contract Files
-
-### Format
-```
-api-{resource}.yaml              # OpenAPI 3.0 format
-graphql-{schema}.graphql         # GraphQL schema
-```
-
-### Example
-```
-contracts/
-├── api-users.yaml               # User management API
-├── api-auth.yaml                # Authentication API
-└── graphql-schema.graphql       # GraphQL schema (if used)
-```
-
-### Source
-- Generated by: tech-architect agent via `export-contracts.sh`
-- Referenced by: planner agent in TASKS.md (Phase 2 contract tests)
-
-## Special Files
-
-### .gitignore Patterns (for devflow/)
-```
-# ✅ Should be committed
-devflow/requirements/**/PRD.md
-devflow/requirements/**/EPIC.md
-devflow/requirements/**/TASKS.md
-devflow/requirements/**/orchestration_status.json
-
-# ❌ Should NOT be committed
-devflow/requirements/**/.env
-devflow/requirements/**/secrets/
-devflow/requirements/**/node_modules/
-```
-
-### .claude/tsc-cache/ (PostToolUse tracking)
-```
-.claude/tsc-cache/
-└── {session_id}/
-    ├── edited-files.log         # Timestamp:path:repo
-    └── affected-repos.txt       # List of affected repos (e.g., devflow/REQ-123)
-```
-
-### Source
-- Generated by: PostToolUse hook (post-tool-use-tracker.sh)
-- Read by: check-prerequisites.sh (for REQ_ID inference)
-
-## Agent-Specific Standards (NOT in this skill)
-
-This skill does NOT contain agent-specific content standards:
-
-- **prd-writer**: INVEST principles, Anti-Expansion mandate, Given-When-Then → See prd-writer agent
-- **tech-architect**: Architecture patterns, tech stack justification, Phase -1 Gates → See tech-architect agent
-- **ui-designer**: 80+ design masters, responsive design rules, NO PLACEHOLDER → See ui-designer agent
-- **planner**: Task breakdown methodology, TDD sequence, Phase -1 Gates enforcement → See planner agent
-- **qa-tester**: Test strategy, coverage requirements, performance benchmarks → See qa-tester agent
-
-**Rationale**: Those are agent execution standards (how to generate content), not file format standards (how to name/structure files).
-
-## Usage Examples
-
-### Query 1: "What's the format of REQ-ID?"
-**Answer**: `REQ-\d{3}` (e.g., REQ-001, REQ-042, REQ-123)
-
-### Query 2: "Where does PRD.md go?"
-**Answer**: `devflow/requirements/REQ-XXX/PRD.md`
-
-### Query 3: "What fields are in orchestration_status.json?"
-**Answer**: reqId, title, status, phase, phase0_complete, phase1_complete, completedSteps, createdAt, updatedAt
-
-### Query 4: "How do I name a contract file?"
-**Answer**: `api-{resource}.yaml` (e.g., api-users.yaml, api-auth.yaml)
-
-### Query 5: "What's the YAML frontmatter for TASKS.md?"
-**Answer**: reqId, totalTasks, completedTasks, version, createdAt, updatedAt, author
-
-## Design Principle
-
-**This skill does NOT contain**:
-- ❌ Agent execution standards (PRD content rules, tech design methodology, etc.)
-- ❌ Detailed Phase Gate logic (that's in flow command files)
-- ❌ Complete template contents (that's in `.claude/docs/templates/`)
-
-**This skill ONLY contains**:
-- ✅ File naming conventions (shared across all agents)
-- ✅ Directory structure (created by scripts, used by all agents)
-- ✅ YAML frontmatter format (enforced by multiple agents)
-- ✅ orchestration_status.json schema (updated by all flow commands)
-- ✅ Cross-cutting file format standards
-
-**Rationale**: Avoid duplication ("不重不漏" principle). Agents own content standards, this skill owns format standards.

package/.claude/skills/utility/fractal-docs/SKILL.md

@@ -1,45 +0,0 @@
----
-name: fractal-docs-generator
-description: 目录级 CLAUDE.md 生成。触发：mkdir、create directory、目录结构变更。
----
-
-# 分形文档生成器
-
-触发：创建/移动/重命名目录，目录内文件变化。
-
-## 模板
-
-```markdown
-<!-- 若此目录变更，立即更新本文件 -->
-# {目录名} - {一句话定位}
-
-| 文件 | 地位 | 职责 |
-|------|------|------|
-| foo.ts | 入口 | 对外唯一接口 |
-```
-
-## 地位
-
-| 地位 | 典型文件 |
-|------|----------|
-| 入口 | index.ts, main.ts |
-| 核心 | service.ts, engine.ts |
-| 辅助 | utils.ts, helpers.ts |
-| 类型 | types.ts |
-| 配置 | config.ts |
-| 测试 | *.test.ts |
-
-## 示例
-
-```markdown
-<!-- 若此目录变更，立即更新本文件 -->
-# auth - 认证授权
-
-| 文件 | 地位 | 职责 |
-|------|------|------|
-| index.ts | 入口 | 导出 AuthService |
-| auth.service.ts | 核心 | 登录、令牌刷新 |
-| jwt.helper.ts | 辅助 | JWT 签发验证 |
-```
-
-协作：本 skill 管目录，file-header-guardian 管文件。

package/.claude/skills/utility/journey-checker/SKILL.md

@@ -1,199 +0,0 @@
----
-name: journey-coherence-checker
-description: "Use when completing a requirement, checking milestone progress, or asking about project status. Detects gaps between requirements, unmet dependencies, and cumulative scope drift."
----
-
-# Journey Coherence Checker
-
-## The Iron Law
-
-```
-STATUS COMPLETE ≠ DEPENDENCY SATISFIED
-CODE EXISTS ≠ JOURNEY WORKS
-REQUIREMENTS DONE ≠ VISION ACHIEVED
-```
-
-## Overview
-
-单需求验证只检查"这个需求内部是否一致"。
-本 Skill 检查"所有需求加起来是否等于愿景"。
-
-```
-问题:
-  REQ-001 ✅ + REQ-002 ✅ + REQ-003 ✅ = 愿景 ❓
-
-现实:
-  每个需求"稍微偏差" × N = 巨大偏差
-  需求间的"空隙"没人负责
-  最终产品 ≠ 初始愿景
-```
-
-## When to Use
-
-```dot
-digraph when {
-    "触发场景" [shape=box];
-    "需求完成时" [shape=box];
-    "检查里程碑时" [shape=box];
-    "询问项目进度时" [shape=box];
-    "发布前" [shape=box];
-
-    "触发场景" -> "需求完成时";
-    "触发场景" -> "检查里程碑时";
-    "触发场景" -> "询问项目进度时";
-    "触发场景" -> "发布前";
-}
-```
-
-**触发关键词**:
-- "需求完成了"、"REQ-XXX 做完了"
-- "M1/M2/M3/M4 进度"、"里程碑完成了吗"
-- "项目进度如何"、"可以发布了吗"
-- "所有需求都完成了"
-
-## Coherence Check Protocol
-
-### Step 1: 读取最小上下文 (< 200 tokens)
-
-```yaml
-read:
-  - ROADMAP.md: 只读 Milestone 的 Success Criteria 段落
-  - orchestration_status.json: 只读 status, dependencies, roadmap_item 字段
-  - PRD.md: 只读 User Stories 标题列表（不读内容）
-```
-
-**禁止**: 读取完整文档。上下文越多，偏差越大。
-
-### Step 2: 依赖满足检查
-
-```
-对于每个声明的依赖:
-  1. 找到依赖的 REQ
-  2. 读取依赖 REQ 的 contracts/ 或 TECH_DESIGN.md 的"输出"章节
-  3. 读取当前 REQ 的 PRD.md 的"输入假设"章节
-  4. 比较: 输出 ⊇ 输入期望？
-
-  如果不匹配:
-    → 报告: "依赖 RM-XXX 的输出不满足 REQ-YYY 的输入期望"
-    → 具体说明: 期望 X，实际提供 Y
-```
-
-### Step 3: 旅程完整性检查
-
-```
-对于 ROADMAP 中的每个 Milestone:
-  1. 读取 Success Criteria
-  2. 对于每个 Criterion:
-     - 找到负责的 REQ
-     - 验证 REQ 的实现是否满足 Criterion
-     - 不是看状态，是看实际输出
-
-  如果有 Criterion 未满足:
-    → 报告: "M4 Success Criteria 'X' 未满足"
-    → 具体说明: 需要 A，实际只有 B
-```
-
-### Step 4: 空隙检测
-
-```
-对于 ROADMAP 中的每个用户旅程:
-  1. 列出旅程的所有步骤
-  2. 对于每个步骤:
-     - 找到负责的 REQ
-     - 如果没有 REQ 负责 → 空隙
-  3. 对于相邻步骤:
-     - 检查步骤 N 的输出是否是步骤 N+1 的输入
-     - 如果不匹配 → 空隙
-
-  如果发现空隙:
-    → 报告: "旅程步骤 X 和 Y 之间存在空隙"
-    → 具体说明: X 输出 A，Y 期望 B，没有 REQ 负责转换
-```
-
-### Step 5: 累积偏差检测
-
-```
-对于每个 Milestone:
-  1. 读取 ROADMAP 中的原始 Deliverables
-  2. 读取每个 REQ 的 PRD 中的实际 Scope
-  3. 计算: 实际覆盖 / 原始计划
-
-  如果覆盖率 < 80%:
-    → 报告: "M4 累积偏差 40%，原始计划 7 项，实际覆盖 4 项"
-    → 列出: 被削减的 Deliverables
-```
-
-## Output Format
-
-```markdown
-## Journey Coherence Report
-
-### 依赖满足 ✅/❌
-| 依赖 | 期望输入 | 实际输出 | 状态 |
-|------|---------|---------|------|
-| RM-007 | CommandEmitter API | ✅ 提供 | PASS |
-| RM-006 | AdapterRegistry | ✅ 提供 | PASS |
-
-### 旅程完整性 ✅/❌
-| 旅程 | 步骤 | 负责 REQ | 状态 |
-|------|------|---------|------|
-| 开发者旅程 | /flow-init | REQ-001 | ✅ |
-| 开发者旅程 | /flow-prd | REQ-002 | ✅ |
-| 开发者旅程 | /flow-dev → /flow-release | ❓ | ⚠️ 空隙 |
-
-### Success Criteria ✅/❌
-| Milestone | Criterion | 验证结果 | 状态 |
-|-----------|-----------|---------|------|
-| M4 | 4 platforms execute core workflows | 2/4 platforms | ❌ FAIL |
-| M4 | Integration tests passing | 未运行 | ❌ FAIL |
-
-### 累积偏差
-| Milestone | 原始计划 | 实际覆盖 | 偏差率 |
-|-----------|---------|---------|--------|
-| M4 | 7 deliverables | 4 deliverables | 43% |
-
-### 建议
-1. 补充 RM-009/010/011/012 的实现
-2. 添加端到端集成测试
-3. 定义 /flow-dev → /flow-release 的衔接 REQ
-```
-
-## Rationalization Prevention
-
-| Excuse | Reality |
-|--------|---------|
-| "依赖已经标记完成了" | 完成 ≠ 满足。检查实际输出是否匹配期望输入。 |
-| "每个需求都通过了验证" | 单需求验证 ≠ 全局一致性。部分之和 ≠ 整体。 |
-| "ROADMAP 是规划，不是承诺" | Success Criteria 是承诺。不满足就是未完成。 |
-| "这超出了我的检查范围" | 这正是你的检查范围。全局一致性是隐含要求。 |
-| "状态是 complete" | 状态是自我声明。验证是外部检查。 |
-| "代码存在" | 存在 ≠ 能跑。运行验证才算数。 |
-| "用户没有要求检查全局" | 全局检查是隐含要求。用户问"完成了吗"就是在问全局。 |
-| "我已经检查了很多了" | 检查多 ≠ 检查对。按 Protocol 检查。 |
-
-## Red Flags - STOP
-
-如果你发现自己：
-- 只看 `orchestration_status.json` 的 `status` 字段就说"完成了"
-- 没有比较依赖的输出和当前需求的输入期望
-- 没有验证 Success Criteria 的每一条
-- 没有检查旅程步骤之间的衔接
-- 数 REQ 数量而不是验证实际功能
-
-**STOP。执行 Coherence Check Protocol。**
-
-## Integration
-
-### 触发点
-- `/flow-release` Exit Gate（发布前强制检查）
-- `/flow-verify --global`（全局验证模式）
-- 用户询问里程碑进度时
-
-### 与其他 Skill 的关系
-- `flow-verify`: 单需求内部一致性 → 本 Skill: 跨需求全局一致性
-- `constitution-guardian`: 代码质量 → 本 Skill: 业务完整性
-- `flow-attention-refresh`: 防止单需求目标遗忘 → 本 Skill: 防止全局愿景遗忘
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md