cc-devflow 4.2.0 → 4.4.1

package/README.md

@@ -1,8 +1,8 @@
 # 🚀 cc-devflow
 
-> Harness-First Requirement Development Flow for Claude Code
+> Roadmap plus PDCA and IDCA skills for agent coding
 
-A comprehensive development workflow system built on Claude Code's official sub-agents, hooks, and settings mechanisms. Transform requirements from planning to code delivery with a deterministic command chain.
+CC-DevFlow is a stripped-down workflow for the agent coding era. It gives you one front-door planning skill, `cc-roadmap`, then lets each requirement enter one of two closed loops: the planning loop `cc-plan -> cc-do -> cc-check -> cc-act`, or the investigation loop `cc-investigate -> cc-do -> cc-check -> cc-act`.
 
 [中文文档](./README.zh-CN.md) | [English](./README.md)
 
@@ -10,826 +10,191 @@ A comprehensive development workflow system built on Claude Code's official sub-
 
 ## 🎯 One-Line Introduction
 
-Harness-first five-stage workflow from requirement setup to release: `/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`.
+CC-DevFlow exposes six visible skills:
 
----
+- `cc-roadmap`: build the project's mid and long-range roadmap
+- `cc-plan`: clarify a roadmap item, design it, and turn it into tasks
+- `cc-investigate`: freeze symptom, reproduction, root cause, and repair tasks before fixing a bug
+- `cc-do`: implement, resume, repair from investigation, and apply review feedback
+- `cc-check`: verify with evidence
+- `cc-act`: ship, sync docs, and feed the result into the next cycle
 
 ## ✨ Core Features
 
-- 🎯 **Harness-First Mainline** - Default chain is `/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`
-- 🔄 **NPM Command Chain** - Flow commands map to `harness:*` runtime operations with checkpoints and resume
-- 📋 **Document-Driven** - Automatic PRD → UI Prototype → EPIC → TASKS → Implementation chain
-- 📝 **Template-Driven** - Self-executable templates (PRD_TEMPLATE, EPIC_TEMPLATE, TASKS_TEMPLATE)
-- 🔄 **Smart Recovery** - `harness:resume` restores interrupted dispatch from persisted checkpoints
-- 🛡️ **Quality Gates** - Automated TypeScript checking, testing, linting, and security scanning
-- 🤖 **Sub-Agent Orchestration** - 12 specialized research agents for different development phases
-- 🎨 **UI Prototype Generation** - Conditional HTML prototype with artistic design inspiration
-- 🔗 **GitHub Integration** - Automated PR creation, branch management, and conventional commits
-- 📊 **Progress Tracking** - Real-time status monitoring and intelligent restart points
-- 🔍 **Consistency Verification** - Enterprise-grade consistency checking with intelligent conflict detection
-- 🧪 **TDD Enforced** - Strict Test-Driven Development with TEST VERIFICATION CHECKPOINT
-- 📜 **Constitution** - 10 Articles governing quality, security, and architecture
-- 🔄 **Autonomous Development** - Ralph × Manus Integration for memory-enhanced continuous iteration
-- 🔌 **Multi-Platform Support** - Compile workflows for Codex, Cursor, Qwen, Antigravity via `npm run adapt`
-- 🔄 **Multi-Module Compiler** - Full module compilation: skills, commands, agents, rules, hooks
-- 🌿 **Git Worktree Integration** - Parallel development with isolated worktrees for 3-5 concurrent Claude sessions
-- 🤝 **Claude Team Integration** - Multi-agent parallel collaboration with automatic task scheduling and conflict detection
-
----
-
-## 💡 Core Concepts
-
-### Hooks System
-
-Real-time quality guardian: PreToolUse blocks non-compliant operations, PostToolUse auto-records changes.
-
-<details>
-<summary>📖 Hooks Details (Click to Expand)</summary>
-
-**Hook Types**:
-
-| Hook | Trigger Timing | Functionality |
-|------|----------------|---------------|
-| **UserPromptSubmit** | When user input is submitted | Intelligently recommends relevant Skills |
-| **PreToolUse** | Before tool use | Blocks non-compliant operations (TDD violations, etc.) |
-| **PostToolUse** | After tool use | Automatically records file changes |
-| **Stop** | When session stops | Provides error handling hints |
-
-**Guardrail Workflow**:
-```
-User edits file → PreToolUse Hook triggers
-  ↓ Path normalization
-  ↓ Rule matching
-  ↓ Content checking
-  ↓ Violation? Block operation : Allow operation
-```
-
-**Skipping Guardrails**:
-```bash
-# Method 1: File marker
-echo "@skip-tdd-check" >> devflow/requirements/REQ-123/TASKS.md
-
-# Method 2: Environment variable
-export SKIP_TDD_ENFORCER=1
-```
+- **Minimal visible surface**: one `cc-roadmap` skill plus two entry loops that share the same `cc-do -> cc-check -> cc-act` tail
+- **Multi-platform CLI restored**: `cc-devflow` is back as the distributable CLI for `.claude` installation plus multi-platform adaptation for Codex, Cursor, Qwen, and Antigravity
+- **skills.sh-compatible skill layout**: `.claude/skills/<skill>/SKILL.md` stays compatible with single-skill distribution on skills.sh
+- **Skill-local resources**: each skill carries its own templates, references, and scripts
+- **Explicit, not hidden**: no default context injection, read the files you actually need
+- **Task-template first**: keep `planning/tasks.md` and `task-manifest.json` as the execution backbone
+- **Skill pack first**: the repository distributes `.claude` skills, playbooks, and assets as one pack
+- **Evidence before done**: verification, doc sync, PR brief, and release note live at the end of the loop
+- **Roadmap-first**: decide medium-range direction once, then execute through PDCA or IDCA
 
-📚 [Complete Hooks Documentation](docs/guides/hooks-system.md)
-</details>
+## 🧠 Mental Model
 
-### Skills System (v4.0 Skills-First Architecture)
-
-Intelligent knowledge base activation with grouped Skills and automatic context injection.
-
-<details>
-<summary>📖 Skills Details (Click to Expand)</summary>
-
-**Skills-First Architecture** (v4.0):
+```text
+cc-roadmap
 
+PDCA: cc-plan -> cc-do -> cc-check -> cc-act
+IDCA: cc-investigate -> cc-do -> cc-check -> cc-act
 ```
-.claude/skills/
-├── workflow.yaml           # Skill dependency graph (OpenSpec-inspired)
-├── workflow/               # 9 Workflow Skills (flow-init, flow-spec, flow-dev, etc.)
-├── domain/                 # 7 Domain Skills (tdd, debugging, brainstorming)
-├── guardrail/              # 3 Guardrail Skills (constitution-guardian, tdd-enforcer)
-└── utility/                # 8 Utility Skills (npm-release, skill-creator)
-```
-
-**Key Skills by Category**:
-
-| Category | Skills | Purpose |
-|----------|--------|---------|
-| **Workflow** | flow-init, flow-spec, flow-dev, flow-verify, flow-release | Core development workflow |
-| **Domain** | tdd, debugging, brainstorming, verification | Domain expertise |
-| **Guardrail** | constitution-guardian, tdd-enforcer | Real-time compliance |
-| **Utility** | npm-release, skill-creator, writing-skills | Development tools |
-
-**Context Injection** (Trellis-inspired):
-- Each Skill has `context.jsonl` defining required context files
-- `inject-skill-context.ts` hook auto-loads context before Skill execution
-- Variable substitution: `{REQ}` → actual requirement ID
 
-📚 [Complete Skills Documentation](docs/guides/skills-system.md)
-</details>
+Use `cc-roadmap` to decide the next 1-3 stages of the product.
 
-### Agent Orchestration
+Use `cc-plan` when the next problem is scope, design, and task freezing.
 
-Dual-layer execution model: Research Agents (11, read-only analysis) + Main Agent (execution).
+Use `cc-investigate` when the next problem is root cause, reproduction, and repair boundary.
 
-<details>
-<summary>📖 Agent Orchestration Details (Click to Expand)</summary>
+Both loops converge into the same `cc-do -> cc-check -> cc-act` tail.
 
-**Execution Model**:
-- **Research Agents**: Read-only analysis, generate Markdown plans and reports
-- **Main Agent (Claude)**: Executes all code operations, owns complete context
-- **Workflow**: Agent Research → Output Plans → Main Agent Executes → Iterate
+The visible state machine lives in the public skills themselves. The pack is intentionally skill-first: routing, reroutes, recovery, and evidence rules are described in `SKILL.md` and `PLAYBOOK.md`, while `lib/skill-runtime/` is limited to shared support code that those skills reuse.
 
-**Tool Distribution**:
-- Research Agents: Read, Grep, Glob (analysis)
-- Main Agent: Edit, Write, Bash, Git (execution)
+## 🚀 Install
 
-📚 [Execution Model Details](docs/architecture/execution-model.md)
-</details>
-
----
-
-## 🚀 Quick Start
-
-### Installation
-
-#### Method 1: Install from npm (Recommended)
-
-```bash
-# Install globally
-npm install -g cc-devflow
-# or
-pnpm add -g cc-devflow
-
-# Initialize in your project
-cc-devflow init
-
-# Compile for specific platform (optional)
-cc-devflow adapt --platform cursor
-cc-devflow adapt --platform codex
-cc-devflow adapt --platform antigravity
-cc-devflow adapt --platform qwen
-```
+The built-in CLI is back to the classic `init + adapt` model.
 
-#### Method 2: Manual Installation
+For the packaged CLI, the default entry stays simple:
 
 ```bash
-pnpm dlx tiged Dimon94/cc-devflow/.claude .claude
+npx cc-devflow init --dir /path/to/your/project
 ```
 
-#### Update
-
-To update to the latest version and synchronize your local project:
+After installation, the restored CLI supports both pack installation and multi-platform adaptation:
 
 ```bash
-# Update globally
-npm install -g cc-devflow@latest
-
-# Update local project files (will overwrite conflicts)
-cc-devflow init
+npx cc-devflow init --dir /path/to/your/project
+npx cc-devflow init --dir /path/to/your/project --force
+npx cc-devflow adapt --cwd /path/to/your/project --platform codex
+npx cc-devflow adapt --cwd /path/to/your/project --platform cursor
+npx cc-devflow adapt --cwd /path/to/your/project --platform qwen
+npx cc-devflow adapt --cwd /path/to/your/project --platform antigravity
 ```
 
-### CLI Usage
-
-```bash
-# Initialize in current directory
-cc-devflow init
-
-# Initialize in specific directory
-cc-devflow init --dir /path/to/project
+Whole-pack installation ships the six visible workflow skills plus the maintenance skills `cc-spec-init` and `cc-simplify`.
+`init --force` now force-upgrades only the managed distributed skills and preserves unrelated project files under `.claude`.
 
-# Compile for specific platform
-cc-devflow adapt --platform codex
-cc-devflow adapt --cwd /path/to/project --platform cursor
+If you are running from a source checkout instead of an installed package, use `node bin/cc-devflow-cli.js ...` or `npm exec -- cc-devflow ...`.
 
-# Run harness runtime directly (for npm script delegation)
-cc-devflow harness release --change-id REQ-123
-```
+## 🧩 skills.sh Distribution
 
-`cc-devflow init` and `cc-devflow adapt` now auto-bootstrap missing `harness:*` npm scripts in `package.json` using portable `cc-devflow harness <subcommand>` entries (no machine-specific absolute paths), so `/flow:*` can execute the runtime chain without manual script patching.
+[skills.sh](https://skills.sh/) is supported only as a distribution channel for the new `.claude` skills.
 
-### Optional Dependencies
+Because skills.sh installs skills one by one, use it to pull the specific skills you want:
 
 ```bash
-# Chinese branch naming support (converts Chinese to pinyin)
-pip install pypinyin
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-roadmap
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-plan
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-investigate
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-do
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-check
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-act
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-spec-init
+npx skills add https://github.com/Dimon94/cc-devflow --skill cc-simplify
 ```
 
-### Verify Installation
+Use `cc-devflow init` when you want the whole `.claude` pack.
 
-```bash
-.claude/scripts/verify-setup.sh
-```
+Use `cc-devflow adapt` when you want generated multi-platform outputs.
 
-### First Requirement
+Use skills.sh when you want to install or refresh a single skill.
 
-```bash
-/flow:init "REQ-001|User Authentication|https://docs.example.com/auth"
-/flow:spec "REQ-001"
-/flow:dev "REQ-001"
-/flow:verify "REQ-001" --strict
-/flow:release "REQ-001"
-```
+## 🔁 Upgrade
 
-<details>
-<summary>🔍 Complete Getting Started Guide (Click to Expand)</summary>
+Refresh the packaged `.claude` bundle with the latest CLI:
 
-**Interactive Demo**:
 ```bash
-python3 .claude/scripts/demo.py
+npx cc-devflow@latest init --dir /path/to/your/project
+npx cc-devflow@latest adapt --cwd /path/to/your/project --all
 ```
 
-**Core Scripts**:
-```bash
-# Environment check
-bash .claude/scripts/check-prerequisites.sh
-
-# View task status
-bash .claude/scripts/check-task-status.sh --verbose
-
-# Mark task complete
-bash .claude/scripts/mark-task-complete.sh T001
-
-# Generate status report
-bash .claude/scripts/generate-status-report.sh --format markdown
-```
+Upgrade installed skills with the skills CLI lifecycle commands:
 
-**Run Tests**:
 ```bash
-# Run all tests
-bash .claude/tests/run-all-tests.sh --scripts
-
-# Constitution tests
-bash .claude/tests/constitution/run_all_constitution_tests.sh
+npx skills check
+npx skills update
 ```
 
-📚 [Complete Getting Started Guide](docs/guides/getting-started.md)
-</details>
-
----
-
-## 📋 Command Quick Reference
+If you only want to refresh one skill immediately, re-run its `npx skills add ... --skill ...` command.
 
-### 🏢 Project-Level Commands
+## 🧱 Repository Format
 
-**Purpose**: Project-wide planning and architecture design, typically executed once per project at the beginning
+CC-DevFlow keeps the `.claude` skill folders compatible with skills.sh single-skill distribution:
 
-| Command | Purpose | Quick Example | Detailed Docs |
-|---------|---------|---------------|---------------|
-| `/core-roadmap` | 🗺️ Generate Product Roadmap | `/core-roadmap` | [→](docs/commands/core-roadmap.md) |
-| `/core-architecture` | 🏗️ Generate System Architecture | `/core-architecture` | [→](docs/commands/core-architecture.md) |
-| `/core-guidelines` | 📘 Generate Project Guidelines | `/core-guidelines` | [→](docs/commands/core-guidelines.md) |
+- one skill per folder
+- one `SKILL.md` per distributed skill
+- YAML frontmatter at the top of each `SKILL.md`
+- public skills declare structured runtime contract fields in frontmatter: `triggers`, `reads`, structured `writes`, `effects`, `entry_gate`, `exit_criteria`, `reroutes`, `recovery_modes`, `tool_budget`
+- bundled local resources beside the skill, such as `PLAYBOOK.md`, `assets/`, `scripts/`, and `references/`
 
-### 📦 Requirement-Level Commands
+Public skills also carry two explicit text contracts:
 
-**Purpose**: Specific requirement development, executed once per requirement (REQ-XXX)
+- `SKILL.md` includes a `Harness Contract` section
+- `PLAYBOOK.md` includes a `Visible State Machine` section
 
-| Command | Purpose | Quick Example | Detailed Docs |
-|---------|---------|---------------|---------------|
-| `/flow:init` | 📦 Initialize Requirement Context | `/flow:init "REQ-123\|Feature"` | [→](.claude/commands/flow/init.md) |
-| `/flow:spec` | 📋 Build Task Manifest | `/flow:spec "REQ-123"` | [→](.claude/commands/flow/spec.md) |
-| `/flow:dev` | 🛠️ Dispatch and Execute Tasks | `/flow:dev "REQ-123"` | [→](.claude/commands/flow/dev.md) |
-| `/flow:verify` | ✅ Run Report Card Gates | `/flow:verify "REQ-123" --strict` | [→](.claude/commands/flow/verify.md) |
-| `/flow:release` | 🚢 Release + Cleanup | `/flow:release "REQ-123"` | [→](.claude/commands/flow/release.md) |
-| `/flow:fix` | 🐛 Systematic Bug Fix | `/flow:fix "BUG-123\|Description"` | [→](.claude/commands/flow/fix.md) |
-| `/flow:new` | ⚠️ Deprecated alias | Use `/flow:init` mainline | [→](.claude/commands/flow/new.md) |
-| `/flow:clarify` | ⚠️ Deprecated | Merged into `/flow:spec` | [→](.claude/commands/flow/clarify.md) |
-| `/flow:checklist` | ⚠️ Deprecated | Use `/flow:verify --strict` | [→](.claude/commands/flow/checklist.md) |
-| `/flow:quality` | ⚠️ Deprecated | Use `/flow:verify` | [→](.claude/commands/flow/quality.md) |
+In this repository, the distributed skill folders are:
 
-📚 [Complete Command Reference](docs/commands/README.md)
-
-<details>
-<summary>🎯 Which Command Should I Use? (Click to Expand)</summary>
-
-```
-Your Scenario:
-├─ Plan product direction? → /core-roadmap
-├─ Design system architecture? → /core-architecture
-├─ Establish coding standards? → /core-guidelines
-├─ Start requirement delivery? → /flow:init "REQ-123|Feature|URLs"
-├─ Generate task manifest? → /flow:spec "REQ-123"
-├─ Execute planned tasks? → /flow:dev "REQ-123"
-├─ Run strict quality gate? → /flow:verify "REQ-123" --strict
-├─ Continue interrupted development? → /flow:restart "REQ-123"
-├─ Check development progress? → /flow:status REQ-123
-├─ Re-check consistency anytime? → /flow:verify "REQ-123"
-├─ Fix production bug? → /flow:fix "BUG-001|Description"
-└─ Ready to release? → /flow:release "REQ-123"
-```
-</details>
-
----
-
-## 🔄 Workflow Diagram
-
-The following Mermaid diagram illustrates the complete cc-devflow workflow, including both project-level and requirement-level processes:
-
-```mermaid
-graph TB
-    Start([Start Project]) --> ProjectLevel{Project-Level Setup}
-
-    ProjectLevel --> CoreRoadmap["/core-roadmap<br/>ROADMAP.md & BACKLOG.md"]
-    ProjectLevel --> CoreArch["/core-architecture<br/>ARCHITECTURE.md"]
-    ProjectLevel --> CoreGuidelines["/core-guidelines<br/>frontend/backend guidelines"]
-    ProjectLevel --> CoreStyle["/core-style<br/>STYLE.md"]
-
-    CoreRoadmap --> ReqLevel
-    CoreArch --> ReqLevel
-    CoreGuidelines --> ReqLevel
-    CoreStyle --> ReqLevel
-
-    ReqLevel([Requirement-Level Development]) --> FlowInit["/flow:init<br/>harness:init + harness:pack"]
-    FlowInit --> FlowSpec["/flow:spec<br/>harness:plan<br/>task-manifest"]
-    FlowSpec --> FlowDev["/flow:dev<br/>harness:dispatch/resume<br/>runtime-events"]
-    FlowDev --> FlowVerify["/flow:verify<br/>harness:verify<br/>report-card"]
-    FlowVerify --> FlowRelease["/flow:release<br/>harness:release/janitor<br/>release-note"]
-    FlowRelease --> End([Release Complete])
-
-    FlowVerify -.->|Can be re-run at any stage| ReqLevel
-
-    style ProjectLevel fill:#e1f5ff
-    style ReqLevel fill:#fff4e1
-    style FlowInit fill:#e8f5e9
-    style FlowSpec fill:#e8f5e9
-    style FlowDev fill:#f3e5f5
-    style FlowVerify fill:#e1bee7
-    style FlowRelease fill:#e0f2f1
-    style End fill:#e3f2fd
-```
-
-**Workflow Notes**:
-- **Project-Level Commands** (light blue): Execute once at project initialization, establish global standards (SSOT)
-- **Requirement-Level Commands** (light orange): Execute once per requirement (REQ-XXX)
-- **Canonical Mainline**: `/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`
-- **Harness Runtime Chain**: Each stage delegates to `npm run harness:*` operations with persisted checkpoints
-- **Unified /flow:spec**: Consolidates planning output into a task manifest
-- **Report Card Gate**: `/flow:verify --strict` blocks release when quality gates fail
-- **TDD Checkpoint**: `/flow:dev` keeps fail-first verification before implementation
-- **Deprecated Commands**: `/flow:new`, `/flow:clarify`, `/flow:checklist`, `/flow:quality` remain as migration stubs
-
----
+- `.claude/skills/cc-roadmap/`
+- `.claude/skills/cc-plan/`
+- `.claude/skills/cc-investigate/`
+- `.claude/skills/cc-do/`
+- `.claude/skills/cc-check/`
+- `.claude/skills/cc-act/`
+- `.claude/skills/cc-spec-init/`
+- `.claude/skills/cc-simplify/`
 
-## 🏗️ System Architecture
+## 🛠️ Use
 
-**Execution Model**: Research Agents (11, read-only) + Main Agent (execution)
-**Document Structure**: Single-track architecture, one requirement directory contains all artifacts
-**Quality Assurance**: Constitution v2.0.0 + TDD Enforcement + Real-time Guardrail
-
-<details>
-<summary>📖 Architecture Details (Click to Expand)</summary>
-
-### Sub-Agents Workflow
-
-```text
-clarify-analyst     → Clarification questions (11-dimension scan)
-prd-writer          → PRD generation (must use PRD_TEMPLATE)
-checklist-agent     → Requirement quality validation (5 dimensions, 6 types) ⭐ NEW
-ui-designer         → UI prototype (conditional trigger)
-tech-architect      → Technical design (Anti-Tech-Creep enforcement)
-planner             → EPIC & TASKS (must use EPIC_TEMPLATE, TASKS_TEMPLATE)
-dev-implementer     → Implementation plan (research only)
-qa-tester           → Test plan + Test report
-security-reviewer   → Security plan + Security report
-release-manager     → Release plan
-```
-
-### Single-Track Architecture
+The skill sequence remains:
 
 ```text
-devflow/
-├── ROADMAP.md               # Product roadmap
-├── ARCHITECTURE.md          # System architecture design
-├── BACKLOG.md               # Requirement backlog
-└── requirements/REQ-123/
-    ├── PRD.md
-    ├── EPIC.md
-    ├── TASKS.md
-    ├── EXECUTION_LOG.md
-    ├── checklists/          # Requirement quality checklists
-    │   ├── ux.md
-    │   ├── api.md
-    │   └── security.md
-    ├── TEST_PLAN.md
-    ├── TEST_REPORT.md
-    ├── SECURITY_PLAN.md
-    ├── SECURITY_REPORT.md
-    └── RELEASE_PLAN.md
+1. cc-roadmap
+2. choose cc-plan or cc-investigate
+3. cc-do
+4. cc-check
+5. cc-act
+6. repeat
 ```
 
-### Quality Gates
+You do not need to remember command names.
 
-- Pre-push Guard (TypeScript, tests, linting, security, build)
-- Report Card Gate (`/flow:verify --strict` before `/flow:release`)
-- Constitution Compliance (enforced at every stage)
-- TDD Checkpoint (TEST VERIFICATION CHECKPOINT)
-- Guardrail Hooks (PreToolUse real-time blocking of non-compliant operations)
+The `cc-devflow` CLI remains the whole-pack installation and adaptation path.
 
-📚 [Complete Architecture Documentation](docs/architecture/)
-</details>
+skills.sh remains the single-skill distribution path for distributed `.claude/skills/*`.
 
----
+## 📦 Outputs
 
-## ⚙️ Configuration
+- `cc-roadmap` writes `devflow/ROADMAP.md` and `devflow/BACKLOG.md`; helper sync can also maintain `devflow/roadmap-tracking.json` as the shared roadmap/backlog truth source
+- `cc-spec-init` writes `devflow/specs/INDEX.md`, capability specs, and `change-meta.json`
+- `cc-plan` writes `planning/design.md`, `planning/tasks.md`, `task-manifest.json`, and `change-meta.json`
+- `cc-investigate` writes `planning/analysis.md`, `planning/tasks.md`, `task-manifest.json`, and `change-meta.json`
+- `cc-do` writes code, tests, task `checkpoint.json`, and workspace scratch runtime
+- `cc-check` writes `report-card.json`
+- `cc-act` writes exactly one final handoff file: `handoff/pr-brief.md`, `handoff/resume-index.md`, or `handoff/release-note.md`
 
-**Minimum Configuration** (`.claude/settings.json`):
+## Durable vs Ephemeral
 
-```json
-{
-  "permissions": {
-    "allowGitOperations": true,
-    "allowNetworkRequests": true,
-    "allowSubprocesses": true
-  }
-}
-```
+- `devflow/specs/` stores durable capability truth: `INDEX.md` plus `capabilities/*.md`.
+- New change directories must be named `REQ-<number>-<description>` for requirements or `FIX-<number>-<description>` for bug fixes; old lowercase directories are compatibility reads only.
+- `devflow/changes/<change>/` stores durable change truth only: `change-state.json`, `change-meta.json`, planning docs, `task-manifest.json`, `team-state.json`, task `checkpoint.json`, `report-card.json`, and one final handoff file.
+- `devflow/workspaces/<change>/` stores ephemeral runtime scratch such as worker assignment, journals, prompts, and session logs.
+- If a file can be regenerated from durable truth, it should not be persisted under `devflow/changes/`.
 
-<details>
-<summary>🔧 Complete Configuration Options (Click to Expand)</summary>
+See [docs/examples/START-HERE.md](./docs/examples/START-HERE.md) for the single entry page to the example set. Example version bindings live in [docs/examples/example-bindings.json](./docs/examples/example-bindings.json).
 
-### Hooks Configuration
+## Principles
 
-```json
-{
-  "hooks": {
-    "PreToolUse": [{
-      "matcher": "Edit|Write",
-      "hooks": [{"type": "command", "command": "..."}]
-    }]
-  }
-}
-```
+- Roadmap before execution
+- Plan before feature code
+- Investigate before bug repair
+- Root cause before fix
+- Evidence before done
+- Ship, then feed the result into the next plan
 
-### Environment Variables
+## Verification
 
 ```bash
-# Flow behavior
-export FLOW_AUTO_APPROVE=false
-export MIN_TEST_COVERAGE=80
-export STRICT_TYPE_CHECKING=true
-
-# Guardrail skip
-export SKIP_TDD_ENFORCER=1
-export SKIP_CONSTITUTION_CHECK=1
+find .claude/skills -mindepth 2 -maxdepth 2 -name SKILL.md | sort
+find .claude/skills -mindepth 2 -maxdepth 3 -type f | sort
+npm run verify
 ```
-
-📚 [Complete Configuration Guide](docs/guides/configuration.md)
-</details>
-
----
-
-## 🧪 Test Coverage
-
-**Script Tests**: 8/8 Passed ✅ (100%)
-**Constitution Tests**: 38/38 Passed ✅ (100%)
-
-```bash
-# Run all tests
-bash .claude/tests/run-all-tests.sh --scripts
-```
-
-<details>
-<summary>📊 Test Framework Details (Click to Expand)</summary>
-
-### Test Suites
-
-| Test Suite | Test Cases | Status |
-|------------|-----------|--------|
-| `test_check_prerequisites` | 18 | ✅ 100% |
-| `test_check_task_status` | 18 | ✅ 100% |
-| `test_common` | 15 | ✅ 100% |
-| `test_mark_task_complete` | 15 | ✅ 100% |
-| `test_setup_epic` | 13 | ✅ 100% |
-| `test_validate_constitution` | 4 | ✅ 100% |
-
-📚 [Test Framework Details](docs/guides/testing-guide.md)
-</details>
-
----
-
-## 📝 Version History
-
-Note: entries before v6.0.0 keep their original command syntax for historical accuracy.
-
-### v6.0.0 (2026-02-18) - Latest Release
-
-**🧩 Harness-First Mainline: Simpler default flow with auditable runtime state**
-
-v6.0.0 simplifies cc-devflow around a single default chain and internal runtime engine:
-
-- **Default Command Chain**
-  - `/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`
-  - Every stage maps to `npm run harness:*` operations for deterministic orchestration
-
-- **Runtime Artifacts**
-  - `context-package.md` + `harness-state.json` for bootstrap state
-  - `task-manifest.json` + `runtime-events.jsonl` for execution trace
-  - `report-card.json` + `release-note.md` for quality and release evidence
-
-- **Deprecated Command Migrations**
-  - `/flow:new` → run the 5-stage mainline explicitly
-  - `/flow:clarify` → merged into `/flow:spec` planning loop
-  - `/flow:checklist` and `/flow:quality` → replaced by `/flow:verify`
-
-**📊 v6.0 Improvements**:
-| Metric | Before | After | Improvement |
-|--------|--------|-------|-------------|
-| Default requirement commands | 8+ mixed paths | 5-stage fixed chain | Simplified |
-| Resume capability | Command-specific | Unified `harness:resume` | Deterministic |
-| Quality evidence | Fragmented outputs | Single report card gate | Auditable |
-
-### v4.7.0 (2026-02-07)
-
-**🤝 Claude Team Integration: Multi-Agent Parallel Collaboration**
-
-v4.7.0 introduces Claude Team integration for multi-agent parallel development:
-
-- **Team Mode for /flow:dev** - Parallel task execution with multiple agents
-  - `--team` flag enables Team mode (default 3 agents)
-  - `--agents N` specifies agent count (2-5)
-  - Automatic task dependency analysis and conflict detection
-  - File conflict tasks assigned to same agent for sequential execution
-
-- **New Hooks** - Team lifecycle management
-  - `TeammateIdle Hook` - Task assignment and scheduling
-  - `TaskCompleted Hook` - Quality verification on completion
-  - Timeout detection and alerting
-
-- **Task Dependency Parser** - Intelligent task analysis
-  - `parse-task-dependencies.js` - Parses TASKS.md format
-  - Recognizes `[P]` parallel markers, `[US*]` user story groups
-  - Phase-based dependency resolution
-
-- **State Recovery** - Checkpoint and resume
-  - `team-state-recovery.sh` - Snapshot and restore Team state
-  - Support for interrupted session recovery
-
-- **New Files**
-  - `.claude/scripts/parse-task-dependencies.js` - Task parser
-  - `.claude/scripts/detect-file-conflicts.sh` - Conflict detection
-  - `.claude/scripts/team-dev-init.sh` - Dev team initialization
-  - `.claude/scripts/team-state-recovery.sh` - State recovery
-  - `.claude/docs/guides/TEAM_MODE_GUIDE.md` - Complete usage guide
-
-**📊 v4.7 Improvements**:
-| Metric | Before | After | Improvement |
-|--------|--------|-------|-------------|
-| Parallel agents | 1 | 3-5 | +400% |
-| Requirement completion time | 90 min | 50 min | -45% |
-| Task scheduling | Manual | Automatic | 100% |
-| Quality verification | Single-point | Distributed | 100% |
-
-### v4.3.0 (2026-02-07)
-
-**🌿 Git Worktree Integration: Parallel Development Support**
-
-v4.3.0 introduces Git Worktree integration for parallel development with isolated Claude Code sessions:
-
-- **Git Worktree Mode (Default)** - Isolated development environments
-  - Creates `../repo-name-REQ-xxx/` worktree directories
-  - Each worktree has independent Claude Code session
-  - Switch between requirements with `cd` instead of `git checkout`
-  - `--branch-only` flag for traditional branch mode
-
-- **New Skill: using-git-worktrees** - Complete worktree management
-  - `worktree-create.sh` - Create new worktree
-  - `worktree-list.sh` - List all worktrees
-  - `worktree-switch.sh` - Switch to worktree
-  - `worktree-cleanup.sh` - Clean up merged worktrees
-  - Shell aliases template (za/zl/zm/zw)
-
-- **Modified Commands**
-  - `/flow:init` - Default worktree mode, `--branch-only` for compatibility
-  - `/flow:release` - Automatic worktree cleanup
-
-**📊 v4.3 Improvements**:
-| Metric | Before | After | Improvement |
-|--------|--------|-------|-------------|
-| Parallel requirements | 1 | 3-5 | +400% |
-| Context switch time | 30s | 1s | -97% |
-| Session isolation | None | Full | 100% |
-
-### v4.1.0 (2026-02-07)
-
-**🎯 Unified Specification Phase: /flow:spec Command**
-
-v4.1.0 merges flow-prd/flow-tech/flow-ui/flow-epic into a single `/flow:spec` command with parallel execution:
-
-- **Unified /flow:spec Command** - One command for entire specification phase
-  - Full Mode: PRD → Tech + UI (parallel) → Epic/Tasks
-  - Quick Mode: `--skip-tech --skip-ui` for small requirements
-  - Backend Only: `--skip-ui`
-  - Frontend Only: `--skip-tech`
-
-- **Parallel Agent Execution** - Tech + UI agents run concurrently
-  - ~35% time reduction in design phase
-  - Shared template components in `_shared/` directory
-
-- **Simplified Workflows** (v4.1)
-  ```
-  Quick (3 steps):    /flow:init --quick → /flow:spec --skip-tech --skip-ui → /flow:dev → /flow:release
-  Standard (4 steps): /flow:init → /flow:spec → /flow:dev → /flow:verify → /flow:release
-  Full (5 steps):     /flow:init → /flow:spec → /flow:dev → /flow:verify --strict → /flow:release
-  ```
-
-- **Deprecations**: `/flow-prd`, `/flow-tech`, `/flow-ui`, `/flow-epic` now deprecated (use `/flow:spec`)
-
-**📊 v4.1 Improvements**:
-| Metric | Before (v4.0) | After (v4.1) | Improvement |
-|--------|---------------|--------------|-------------|
-| Command calls | 4 | 1 | -75% |
-| Design phase time | 8-12 min | 5-8 min | -35% |
-| Entry/Exit Gate code | ~280 lines | ~100 lines | -64% |
-
-### v4.0.0 (2026-02-07)
-
-**🏗️ Skills-First Architecture: Unified Skills with Context Injection**
-
-v4.0.0 introduces a major architectural refactor, reorganizing 135 files into a unified Skills-First Architecture inspired by Trellis and OpenSpec:
-
-- **Skills-First Architecture** - All Skills organized into 4 groups
-  - `workflow/`: 9 core workflow Skills (flow-init, flow-spec, flow-dev, etc.)
-  - `domain/`: 7 domain expertise Skills (tdd, debugging, brainstorming, verification)
-  - `guardrail/`: 3 real-time compliance Skills (constitution-guardian, tdd-enforcer)
-  - `utility/`: 8 development tool Skills (npm-release, skill-creator, writing-skills)
-
-- **JSONL Context Injection** (Trellis-inspired)
-  - Each Skill has `context.jsonl` defining required context files
-  - `inject-skill-context.ts` hook auto-loads context before Skill execution
-  - Variable substitution: `{REQ}` replaced with actual requirement ID
-  - Optional files supported with `"optional": true`
-
-- **workflow.yaml Dependency Graph** (OpenSpec-inspired)
-  - Defines Skill dependencies with `requires` and `generates`
-  - File existence state detection for workflow status
-  - Clear visualization of Skill execution order
-
-- **Self-Contained Skills**
-  - Each Skill directory contains: SKILL.md + context.jsonl + scripts/ + references/ + assets/
-  - SKILL.md limited to <500 lines for focused instructions
-  - Agent instructions moved to `references/` subdirectory
-  - Templates moved to `assets/` subdirectory
-
-- **Multi-Module Cross-Platform Compiler** (v3.0)
-  - Complete multi-module compilation: skills, commands, agents, rules, hooks
-  - Platform-specific output formats:
-    - **Codex**: `.codex/skills/`, `.codex/prompts/`, `AGENTS.md`
-    - **Cursor**: `.cursor/rules/*.mdc`, `.cursor/subagents/`, `hooks.json`
-    - **Qwen**: `.qwen/commands/*.toml`, `.qwen/agents/`, `CONTEXT.md`
-    - **Antigravity**: `.agent/skills/`, `.agent/workflows/`, `.agent/rules/`
-  - `context.jsonl` compilation-time expansion with platform-specific formats
-  - 197 tests passing (24 new multi-module tests)
-
-**📊 v4.0 Improvements**:
-| Metric | Before | After | Improvement |
-|--------|--------|-------|-------------|
-| Maintenance points | 4 directories | 1 directory | -75% |
-| Context loading | Manual full load | On-demand auto | -70% tokens |
-| Dependency visibility | Implicit | Explicit (workflow.yaml) | +100% |
-| Platform module support | Commands only | All modules | +400% |
-
-**📁 New Files**:
-- `.claude/skills/workflow.yaml` - Skill dependency graph
-- `.claude/hooks/inject-skill-context.ts` - Context injection hook
-- `.claude/skills/workflow/*/context.jsonl` - Per-Skill context definitions
-- `devflow/spec/{frontend,backend,shared}/index.md` - Specification indexes
-- `lib/compiler/context-expander.js` - Context.jsonl expansion module
-- `lib/compiler/__tests__/multi-module-emitters.test.js` - Multi-module tests
-
-### v2.3.0 (2026-01-08)
-
-**🛡️ Discipline System: Iron Law + Rationalization Defense + Pressure Testing**
-
-v2.3.0 upgrades the Constitution from a "document" to an "executable discipline system", borrowing best practices from superpowers project:
-
-- **Iron Law + Rationalization Tables** - Pre-block AI Agent rationalization attempts
-  - Each of 10 Constitution Articles now has an Iron Law (absolute prohibition)
-  - Rationalization Tables with `| Excuse | Reality |` format
-  - Red Flags for AI self-check triggers
-  - Centralized `rationalization-library.md` for all rationalizations
-
-- **Two-Stage Code Review** - `/flow-review` command (NEW)
-  - Stage 1: Spec Compliance (don't trust implementer reports, read code directly)
-  - Stage 2: Code Quality (only runs after Stage 1 passes)
-  - `spec-reviewer.md` and `code-quality-reviewer.md` agents
-
-- **Verification Before Completion** - Evidence before assertions
-  - `verification-before-completion` skill
-  - `verify-gate.sh` script for all flow exit gates
-  - No completion claims without fresh verification evidence
-
-- **Systematic Debugging** - `/flow-fix` enhanced with 4-phase debugging
-  - Phase 1: Root Cause Investigation (NO FIXES YET)
-  - Phase 2: Pattern Analysis
-  - Phase 3: Hypothesis and Testing
-  - Phase 4: TDD Implementation
-  - `flow-debugging` and `flow-tdd` skills
-
-- **Brainstorming Integration** - `/flow:init` now includes brainstorming
-  - `BRAINSTORM.md` as requirement "North Star"
-  - `/flow:spec` requires BRAINSTORM alignment check
-  - `flow-brainstorming` skill
-
-- **Pressure Testing Framework** - TDD for Skills
-  - `tests/pressure-scenarios/` with 4 scenarios
-  - Tests AI behavior under time/sunk cost/authority/exhaustion pressure
-  - `run-pressure-tests.sh` runner
-
-- **Skills Fusion** - Superpowers skills migrated to local
-  - `flow-tdd`, `flow-debugging`, `flow-receiving-review`, `flow-finishing-branch`
-  - All `superpowers:xxx` references replaced with local skills
-
-- **Ralph × Manus Integration** - Autonomous development with memory (NEW)
-  - Merged into `/flow:dev` (Autonomous by default)
-  - `flow-attention-refresh` skill with 4 refresh protocols
-  - `ERROR_LOG.md` structured error tracking
-  - `research/attempts/` failure trace recording
-  - Stop Hook for self-referential loops
-  - Manus method in `/flow:init` Stage 2.5 Research
-  - Target: ≥85% task completion rate without human intervention
-
-**📋 Constitution v2.1.0**:
-- All 10 Articles now have Iron Law + Rationalization Defense + Red Flags
-- Cross-reference to `rationalization-library.md`
-
-**📁 New Files**:
-- `.claude/commands/util/cancel-ralph.md` - Cancel Ralph loop command
-- `.claude/skills/flow-attention-refresh/SKILL.md` - 4 attention refresh protocols
-- `.claude/hooks/ralph-stop-hook.sh` - Stop Hook for self-referential loops
-- `.claude/hooks/hooks.json` - Hook registration configuration
-- `.claude/scripts/setup-ralph-loop.sh` - Ralph state initialization script
-- `.claude/docs/templates/ERROR_LOG_TEMPLATE.md` - Execution error log format
-- `.claude/docs/templates/ATTEMPT_TEMPLATE.md` - Research attempt log format
-- `.claude/agents/spec-reviewer.md` - Stage 1 spec compliance reviewer
-- `.claude/agents/code-quality-reviewer.md` - Stage 2 code quality reviewer
-- `.claude/commands/flow-review.md` - Two-stage review command (legacy, replaced by `.claude/commands/flow/quality.md`)
-- `.claude/rules/rationalization-library.md` - Centralized rationalization defense
-- `.claude/scripts/verify-gate.sh` - Exit gate verification script
-- `.claude/skills/flow-brainstorming/` - Brainstorming skill
-- `.claude/skills/flow-debugging/` - Systematic debugging skill
-- `.claude/skills/flow-tdd/` - TDD enforcement skill
-- `.claude/skills/flow-receiving-review/` - Review feedback handling skill
-- `.claude/skills/flow-finishing-branch/` - Branch completion decision skill
-- `.claude/skills/verification-before-completion/` - Completion verification skill
-- `tests/` - Pressure testing framework
-
-### v2.2.0 (2025-12-19)
-
-**🔌 Multi-Platform Adaptation: Agent Adapter Architecture + Command Emitter**
-
-v2.2.0 introduces comprehensive multi-platform support, enabling cc-devflow workflows to run on multiple AI coding assistants:
-
-- **Agent Adapter Architecture (REQ-004)** - Pluggable adapter layer for platform differences
-  - Unified Agent Adapter abstraction (environment detection, command execution, capability declaration)
-  - Adapter Registry with auto-detection and explicit override support
-  - Built-in adapters: Claude Code (default), Codex CLI, Cursor, Qwen, Antigravity
-  - Security-first design: capability allow-list with default deny for high-risk operations
-  - Structured logging for debugging and auditing
-
-- **Command Emitter Compiler (REQ-005)** - Single Source of Truth compilation
-  - `.claude/` as SSOT, compiles to platform-native formats
-  - `npm run adapt` CLI for multi-platform compilation
-  - Supported platforms: Codex (`.codex/`), Cursor (`.cursor/`), Qwen (`.qwen/`), Antigravity (`.agent/`)
-  - Placeholder expansion: `{SCRIPT:*}`, `{TEMPLATE:*}`, `{GUIDE:*}`, `{AGENT_SCRIPT}`, `$ARGUMENTS`
-  - Template/Guide inlining with automatic content embedding
-  - Resource copying with path rewriting (scripts, templates, guides → platform directories)
-  - Manifest-based incremental compilation with drift detection
-
-- **Adapter Compiler (REQ-006)** - Multi-platform rules entry file generation
-  - Platform-specific rules emitters for 4 platforms (Cursor MDC, Codex SKILL.md, Qwen TOML, Antigravity with 12K splitting)
-  - Skills registry compilation (merges `skill-rules.json` + `skill.md` metadata)
-  - Manifest v2.0 extension with `skills` and `rulesEntry` tracking
-  - `--rules` and `--skills` CLI options for selective compilation
-  - **Bug Fix**: Disabled template inlining by default (keeps path references instead of inline expansion)
-  - 173 tests, 87% coverage for new modules
-
-**📦 New CLI Tool**:
-```bash
-npm run adapt                        # Compile for all platforms
-npm run adapt -- --platform codex    # Compile for specific platform
-npm run adapt -- --check             # Check for drift without compiling
-npm run adapt -- --verbose           # Show detailed output
-```
-
-### v2.1.0 (2025-11-07)
-
-**🏢 Core Breakthrough: Introduction of Project-Level Commands**
-
-v2.1.0's core breakthrough is the introduction of **Project-Level Commands**, forming a two-tier system with previous **Requirement-Level Commands**:
-
-- **Project-Level Commands** - Project-wide planning and architecture design (executed once per project at the beginning)
-  - `/core-roadmap` - Interactive product roadmap generation (6-stage dialogue)
-  - `/core-architecture` - 4 architecture diagram generation (Mermaid format)
-  - `/core-guidelines` - Project guidelines generation (frontend/backend separation)
-
-- **Requirement-Level Commands Enhancement** - Stage 1.5 Roadmap & Architecture context loading (flow-init)
-  - Automatically load project-level context when initializing requirements
-  - Automatic requirement-to-roadmap mapping (RM-ID, Milestone, Quarter)
-  - Automatic architecture context association (Feature Layer, Tech Stack, Module)
-
-**📚 Documentation Improvements**:
-- README complete refactoring (complete TOC + folding + external documentation links)
-- Added 25+ detailed documents
-
-📋 [Complete Changelog](CHANGELOG.md)
-
----
-
-## 🤝 Contributing & Support
-
-**Contributing**: [Contributing Guide](CONTRIBUTING.md)
-**Issues**: [GitHub Issues](https://github.com/Dimon94/cc-devflow/issues)
-**Documentation**: [Complete Documentation](docs/)
-
----
-
-## 📄 License
-
-MIT License - See [LICENSE](LICENSE) file
-
----
-
-**🌟 Star this repository if cc-devflow helps streamline your development workflow!**