cc-devflow 4.3.0 → 4.4.1

package/.claude/skills/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/finishing-branch/SKILL.md

@@ -1,189 +0,0 @@
----
-name: flow-finishing-branch
-description: "Decide how to complete a development branch: merge, PR, squash, or cleanup."
----
-
-# Flow Finishing Branch - 分支完成决策
-
-## Overview
-
-When development work is complete, you need to decide how to integrate it. This skill guides that decision.
-
-## Decision Options
-
-### A) Fast-forward Merge
-
-```yaml
-When to use:
-  - Small changes (< 5 files)
-  - Single developer
-  - No review needed
-  - Clean commit history
-
-Command:
-  git checkout main
-  git merge --ff-only feature/xxx
-  git branch -d feature/xxx
-
-Pros:
-  - Fast
-  - Clean history
-  - No merge commit
-
-Cons:
-  - No review record
-  - No CI verification
-```
-
-### B) Create PR (Recommended)
-
-```yaml
-When to use:
-  - Team projects
-  - Need review record
-  - CI verification required
-  - Production code
-
-Command:
-  git push -u origin feature/xxx
-  gh pr create --title "..." --body "..."
-
-Pros:
-  - Review record
-  - CI verification
-  - Discussion thread
-  - Audit trail
-
-Cons:
-  - Takes longer
-  - Requires reviewer
-```
-
-### C) Squash and Merge
-
-```yaml
-When to use:
-  - Many small commits
-  - Messy commit history
-  - Want single commit in main
-
-Command:
-  gh pr merge --squash
-
-Pros:
-  - Clean main history
-  - Single logical commit
-  - Hides WIP commits
-
-Cons:
-  - Loses detailed history
-  - Harder to bisect
-```
-
-### D) Cleanup Only
-
-```yaml
-When to use:
-  - Work was abandoned
-  - Experiment failed
-  - Requirements changed
-
-Command:
-  git checkout main
-  git branch -D feature/xxx
-  git push origin --delete feature/xxx  # if pushed
-
-Pros:
-  - Clean slate
-  - No dead branches
-
-Cons:
-  - Work is lost (unless needed later)
-```
-
-## Decision Matrix
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│                    Decision Matrix                          │
-├─────────────────────────────────────────────────────────────┤
-│                                                             │
-│  Files Changed    Review Needed    History Clean    Action  │
-│  ─────────────    ─────────────    ─────────────    ──────  │
-│  < 5              No               Yes              A) FF   │
-│  < 5              No               No               C) Sq   │
-│  Any              Yes              Yes              B) PR   │
-│  Any              Yes              No               C) Sq   │
-│  N/A              N/A              N/A (abandoned)  D) Del  │
-│                                                             │
-└─────────────────────────────────────────────────────────────┘
-```
-
-## Pre-Completion Checklist
-
-Before choosing any option, verify:
-
-```yaml
-□ All tests pass
-□ Build succeeds
-□ No lint errors
-□ Documentation updated (if needed)
-□ EXECUTION_LOG.md updated
-□ No uncommitted changes
-```
-
-## The Process
-
-```yaml
-1. Verify completion
-   → Run tests, build, lint
-   → Check all tasks done
-
-2. Assess the work
-   → How many files changed?
-   → Is review needed?
-   → Is commit history clean?
-
-3. Choose option
-   → Use decision matrix
-   → Default to PR if unsure
-
-4. Execute
-   → Run appropriate commands
-   → Verify success
-
-5. Cleanup
-   → Delete local branch
-   → Delete remote branch (if not PR)
-```
-
-## Rationalization Prevention
-
-| Excuse | Reality |
-|--------|---------|
-| "PR is overkill" | PR provides audit trail. Use it. |
-| "I'll review my own code" | Self-review misses issues. Get another pair of eyes. |
-| "History doesn't matter" | History helps debugging. Keep it clean. |
-| "Just merge it" | Verify first. Merge second. |
-
-## Integration with flow-release
-
-This skill is used in `/flow-release` to decide branch handling:
-
-```yaml
-/flow-release execution:
-  1. Verify all gates pass
-  2. Load this skill
-  3. Present options to user
-  4. Execute chosen option
-  5. Update status
-```
-
-## Cross-Reference
-
-- [flow-release.md](../../commands/flow-release.md) - Release command
-- [verification-before-completion](../verification-before-completion/SKILL.md) - Verification skill
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

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

@@ -1,16 +0,0 @@
-# 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/flow-dev/SKILL.md

@@ -1,94 +0,0 @@
----
-name: flow-dev
-description: 'Execute task-manifest with dependency-aware parallel dispatch and checkpoint recovery. Use when implementing planned tasks for a requirement.'
----
-
-# Flow-Dev Skill
-
-> [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
-
-## Purpose
-
-执行 `task-manifest.json` 中的任务，默认并行调度并写入 checkpoint/events 供恢复。
-
-## Long-Running Harness Protocol（Initializer/Worker/Done Gate）
-
-`/flow:dev` 是最长链路阶段，必须严格执行“先读状态、再增量、后留证据”。
-
-### Session Start（禁止盲跑）
-
-每个窗口开始时先同步以下信息：
-- `devflow/requirements/${REQ_ID}/session-checklist.json`（若存在）
-- `devflow/requirements/${REQ_ID}/session-progress.md`（若存在）
-- `devflow/requirements/${REQ_ID}/session-handoff.md`（若存在）
-- `devflow/requirements/${REQ_ID}/task-manifest.json`
-- `.harness/runtime/${REQ_ID}/**/checkpoint.json` 与 `events.jsonl`（若存在）
-
-然后执行一次基础健康检查：
-1. 不存在损坏的 `running` 残留状态
-2. 上轮失败任务与失败原因可定位
-
-### Worker Session（最小可执行前沿）
-
-单窗口仅推进一个最小前沿：
-- 仅处理当前 `dependsOn` 已满足的一组任务
-- 每完成一组任务即写入 checkpoint/events
-- 遇到失败立即收敛原因并记录，不并行扩散新的失败面
-
-会话收尾必须：
-1. 更新 `task-manifest.json` 状态
-2. 更新 `session-progress.md` 与 `session-handoff.md`
-3. 推荐提交一个可回滚的最小 git commit（若仓库策略允许）
-
-### Done Gate
-
-仅当以下条件满足才标记 `flow:dev` 完成：
-- 全部任务为 `passed` 或 `skipped`
-- 无 `running`/`failed` 残留
-- `session-checklist.json` 中 `flow:dev.passes == true`
-
-## Input Format
-
-```bash
-/flow:dev "REQ_ID" [--parallel N] [--resume] [--max-retries N]
-```
-
-## Execution Steps
-
-1. 解析参数：
-   - 默认 `parallel = 3`
-   - 默认不 resume
-2. 分支执行：
-   - 普通执行：
-
-```bash
-npm run harness:dispatch -- --change-id "${REQ_ID}" --parallel ${PARALLEL} [--max-retries ${MAX_RETRIES}]
-```
-
-   - 恢复执行：
-
-```bash
-npm run harness:resume -- --change-id "${REQ_ID}" --parallel ${PARALLEL} [--max-retries ${MAX_RETRIES}]
-```
-
-3. 检查执行结果：
-   - `task-manifest.json` 状态更新
-   - `.harness/runtime/${REQ_ID}/<TASK_ID>/events.jsonl`
-   - `.harness/runtime/${REQ_ID}/<TASK_ID>/checkpoint.json`
-
-## Exit Criteria
-
-- 所有任务状态为 `passed` 或 `skipped`
-- 没有 `running` 残留状态
-
-## Failure Handling
-
-- 若存在 `failed` 任务：
-  1. 修复失败原因
-  2. 重新运行 `--resume`
-
-## Next Step
-
-```bash
-/flow:verify "${REQ_ID}"
-```