cc-devflow 4.1.5 → 4.2.0

package/docs/commands/flow-new.md

@@ -1,274 +1,39 @@
-# `/flow-new` - Start New Requirement Development
+# `/flow-new` - Deprecated Alias
 
 [中文文档](./flow-new.zh-CN.md) | [English](./flow-new.md)
 
----
+`/flow-new` is retained only for backward compatibility and should not be used for new workflows.
 
-## 📋 Overview
+## Canonical Mainline
 
-One-command launch of complete requirement development flow, from PRD generation to code delivery automated workflow.
-
-## 🎯 Syntax
-
-```bash
-/flow-new "REQ-ID|Feature Title|Plan URLs"
-```
-
-## 📖 Parameters
-
-| Parameter | Description | Required | Example | Notes |
-|-----------|-------------|----------|---------|-------|
-| **REQ-ID** | Requirement number | ✅ | `REQ-123` | Must be unique, format REQ-NNN |
-| **Feature Title** | Brief description | ✅ | `User Authentication Feature` | Used for Git branch naming and document titles |
-| **Plan URLs** | External reference links | ❌ | `https://docs.example.com/auth` | Optional, separate multiple with `\|` |
-
-## 🎬 Use Cases
-
-### ✅ Recommended Scenarios
-
-| Scenario | Description |
-|----------|-------------|
-| Launch brand new feature development | New feature from scratch |
-| First-time requirement document creation | Need to generate PRD, EPIC, TASKS documents |
-| Long-term project launch | Projects lasting > 1 week |
-
-### ❌ Not Recommended Scenarios
-
-| Scenario | Alternative |
-|----------|------------|
-| Resume interrupted development | Use `/flow-restart "REQ-123"` |
-| Fix bugs | Use `/flow-fix "BUG-001\|Description"` |
-| Only initialize directory structure | Use `/flow-init "REQ-123\|Title"` |
-| Quick prototype validation | Use `/flow-ideate "Idea description"` |
-
-## 🔄 Execution Flow
-
-```text
-/flow-new "REQ-123|User Authentication|https://docs.example.com/auth"
-  ↓
-Stage 1: Initialize (flow-init)
-  ├─ Create requirement directory structure
-  ├─ Load roadmap and architecture context (if exists)
-  ├─ Create Git branch feature/REQ-123-user-auth
-  └─ Initialize orchestration_status.json
-  ↓
-Stage 2: PRD Generation (prd-writer agent)
-  ├─ Analyze external reference links
-  ├─ Research existing codebase
-  ├─ Generate PRD.md using PRD_TEMPLATE
-  └─ Record to EXECUTION_LOG.md
-  ↓
-Stage 3: UI Prototype Generation (ui-designer agent, conditional)
-  ├─ Detect if PRD contains UI requirements
-  ├─ If UI requirements exist, generate UI_PROTOTYPE.html
-  ├─ Responsive design (320px/768px/1024px)
-  └─ Complete interaction states and real images
-  ↓
-Stage 4: Technical Design (tech-architect agent)
-  ├─ Analyze PRD + existing codebase
-  ├─ Design technical solution (avoid over-engineering)
-  ├─ Generate TECH_DESIGN.md
-  └─ Anti-Tech-Creep enforcement
-  ↓
-Stage 4.5: Requirement Quality Check (checklist-agent, optional) ⭐ NEW
-  ├─ Generate type-specific checklists (ux, api, security, etc.)
-  ├─ Validate 5 quality dimensions
-  ├─ Calculate completion percentage
-  └─ 80% threshold gate before EPIC
-  ↓
-Stage 5: EPIC & TASKS Generation (planner agent)
-  ├─ Analyze PRD + TECH_DESIGN
-  ├─ Generate EPIC.md using EPIC_TEMPLATE
-  ├─ Generate TASKS.md using TASKS_TEMPLATE
-  └─ Tasks ordered in TDD sequence (Phase 1-5)
-  ↓
-Stage 6: Development (dev-implementer agent + main agent execution)
-  ├─ dev-implementer generates IMPLEMENTATION_PLAN.md
-  ├─ Main agent executes code implementation
-  ├─ Follow TDD: tests first, then implementation
-  └─ Real-time update TASKS.md progress
-  ↓
-Stage 7: QA (qa-tester agent)
-  ├─ Generate TEST_PLAN.md
-  ├─ Execute tests (unit tests, integration tests)
-  ├─ Generate TEST_REPORT.md
-  └─ Security scan (security-reviewer agent)
-  ↓
-Stage 8: Release (release-manager agent)
-  ├─ Generate RELEASE_PLAN.md
-  ├─ Check release readiness
-  ├─ Create Pull Request
-  └─ Create Git Tag (optional)
-```
-
-## 💡 Examples
-
-### Example 1: Basic Usage
-
-```bash
-/flow-new "REQ-001|User Login Feature"
-```
-
-**Output**:
-```
-devflow/requirements/REQ-001/
-├── orchestration_status.json
-├── EXECUTION_LOG.md
-├── PRD.md
-├── EPIC.md
-├── TASKS.md
-└── ... (other documents)
-```
-
-**Git Branch**: `feature/REQ-001-user-login`
-
-### Example 2: With External Reference
-
-```bash
-/flow-new "REQ-002|Payment Integration|https://stripe.com/docs/api"
-```
-
-**Effect**:
-- PRD will reference Stripe API documentation
-- Technical design will consider Stripe integration solution
-- Task breakdown will include Stripe SDK integration tasks
-
-### Example 3: Multiple Reference Links
-
-```bash
-/flow-new "REQ-003|Data Analytics|https://doc1.com|https://doc2.com"
-```
-
-**Effect**:
-- System will fetch content from both external links
-- PRD will reference both documents comprehensively
-- `research/` directory will save fetched content
-
-## 📂 Output File Structure
-
-After executing `/flow-new`, complete requirement directory is generated:
-
-```
-devflow/requirements/REQ-XXX/
-├── orchestration_status.json    # State management (stage, progress, timestamps)
-├── EXECUTION_LOG.md             # Complete audit trail
-├── PRD.md                       # Product Requirements Document
-├── UI_PROTOTYPE.html            # UI Prototype (conditional generation)
-├── TECH_DESIGN.md               # Technical Design Document
-├── checklists/                  # Requirement quality checklists ⭐ NEW
-│   ├── ux.md                    # UX checklist
-│   ├── api.md                   # API checklist
-│   └── security.md              # Security checklist
-├── EPIC.md                      # Epic planning and breakdown
-├── TASKS.md                     # Single unified task list
-├── tasks/                       # Task execution artifacts
-│   ├── TASK_001.completed
-│   ├── TASK_002.completed
-│   └── IMPLEMENTATION_PLAN.md
-├── research/                    # External research materials (MCP fetched)
-├── TEST_PLAN.md                 # QA testing strategy
-├── TEST_REPORT.md               # QA testing results
-├── SECURITY_PLAN.md             # Security review plan
-├── SECURITY_REPORT.md           # Security scan results
-└── RELEASE_PLAN.md              # Release checklist
-```
-
-## 🔗 Related Commands
-
-- [`/flow-init`](./flow-init.md) - Only initialize requirement structure (no subsequent stages)
-- [`/flow-checklist`](../../.claude/commands/flow-checklist.md) - Requirement quality check (80% gate before EPIC) ⭐ NEW
-- [`/flow-restart`](./flow-restart.md) - Resume interrupted development
-- [`/flow-status`](./flow-status.md) - View requirement development progress
-- [`/flow-verify`](./flow-verify.md) - Verify document consistency
-- [`/flow-fix`](./flow-fix.md) - Bug fix workflow (alternative to flow-new)
-
-## ⚙️ Configuration Options
-
-### Environment Variables
+Use the explicit 5-stage chain:
 
 ```bash
-# Quality gate configuration
-export MIN_TEST_COVERAGE=80              # Minimum test coverage threshold
-export STRICT_TYPE_CHECKING=true         # Enforce strict TypeScript checking
-
-# Flow control
-export FLOW_AUTO_APPROVE=false           # Whether quality gates require manual approval
-export FLOW_SKIP_BACKGROUND=false        # Whether to skip background process startup
-
-# MCP integration
-export WEBFETCH_TIMEOUT=30               # External link fetch timeout (seconds)
-export ALLOWED_DOMAINS=""                # Allowed domains whitelist
+/flow:init "REQ-123|Feature Title|https://plan.example.com"
+/flow:spec "REQ-123"
+/flow:dev "REQ-123"
+/flow:verify "REQ-123" --strict
+/flow:release "REQ-123"
 ```
 
-### Hooks Configuration
-
-Hooks in `.claude/settings.json` will be triggered during flow-new execution:
-
-- **PreToolUse**: Block non-compliant operations (e.g., violating TDD order)
-- **PostToolUse**: Auto-record file changes to EXECUTION_LOG.md
-- **Constitution Compliance**: Enforce Constitution v2.0.0 at every stage
-
-## 🚨 Common Issues
-
-### Q1: What if flow-new gets interrupted halfway?
+## Why `/flow-new` Is Deprecated
 
-**A**: Use `/flow-restart "REQ-123"` to auto-detect restart point and continue execution.
+- Hidden one-shot behavior made failure recovery hard.
+- Stage boundaries were unclear for long-running agent execution.
+- Quality gate and resume behavior are now standardized in `/flow:verify` and `/flow:dev --resume`.
 
-### Q2: How to skip certain stages (e.g., UI prototype)?
-
-**A**: UI prototype is conditionally triggered. If PRD doesn't contain UI requirements, it will be automatically skipped. Other stages don't support skipping yet.
-
-### Q3: What if external link fetch fails?
-
-**A**:
-1. Check network connection
-2. Check `ALLOWED_DOMAINS` configuration
-3. Increase `WEBFETCH_TIMEOUT` timeout
-4. Manually save reference content to `research/` directory
-
-### Q4: Generated PRD doesn't meet expectations?
-
-**A**:
-1. Provide more detailed external reference links
-2. Manually edit PRD.md after execution
-3. Use `/flow-restart "REQ-123" --from=prd` to regenerate
-
-### Q5: Task order doesn't meet TDD requirements?
-
-**A**: This is a bug. TASKS.md must follow Phase 1-5 TDD order:
-- Phase 1: Test infrastructure
-- Phase 2: Unit test writing
-- Phase 3: Integration test writing
-- **Phase 3.5: TEST VERIFICATION CHECKPOINT** (blocking point)
-- Phase 4: Feature implementation
-- Phase 5: Documentation and cleanup
-
-If order is incorrect, please report a bug.
-
-## 📊 Performance Estimates
-
-| Requirement Complexity | Estimated Time | File Count | Token Usage |
-|------------------------|----------------|------------|-------------|
-| Simple (CRUD) | 5-10 minutes | 10-15 files | ~20K tokens |
-| Medium (API Integration) | 15-30 minutes | 15-20 files | ~50K tokens |
-| Complex (Multi-module) | 30-60 minutes | 20-30 files | ~100K tokens |
-
-**Note**: Actual time depends on codebase size, number of external links, agent response speed, etc.
-
-## 🔍 Debug Mode
-
-Enable verbose logging to view execution details:
-
-```bash
-export FLOW_DEBUG=1
-/flow-new "REQ-123|Test Feature"
-```
+## Legacy to Current Mapping
 
-Log file location: `.claude/logs/flow-*.log`
+| Legacy | Current |
+|--------|---------|
+| `/flow-new` | `/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release` |
+| `/flow-restart` | `/flow:dev --resume` or `/flow:status` guided recovery |
+| `/flow-quality` | `/flow:verify` |
 
-## 📚 Deep Reading
+## Related Commands
 
-- [Execution Model Details](../architecture/execution-model.md)
-- [Sub-Agent Workflow](../architecture/agent-workflow.md)
-- [Quality Gates System](../architecture/quality-gates.md)
-- [Constitution v2.0.0](../architecture/constitution.md)
+- [`/flow:init`](./flow-init.md)
+- [`/flow:spec`](../../.claude/commands/flow/spec.md)
+- [`/flow:dev`](../../.claude/commands/flow/dev.md)
+- [`/flow:verify`](../../.claude/commands/flow/verify.md)
+- [`/flow:release`](../../.claude/commands/flow/release.md)

package/docs/commands/flow-new.zh-CN.md

@@ -1,270 +1,39 @@
-# `/flow-new` - 启动新需求开发
+# `/flow-new` - 已废弃别名
 
-## 📋 概述
+[English](./flow-new.md) | [中文文档](./flow-new.zh-CN.md)
 
-一键启动完整的需求开发流程，从 PRD 生成到代码交付的完整自动化工作流。
+`/flow-new` 仅为兼容保留，不再作为主流程入口。
 
-## 🎯 语法
+## 当前主链
 
-```bash
-/flow-new "REQ-ID|功能标题|计划URLs"
-```
-
-## 📖 参数详解
-
-| 参数 | 说明 | 必填 | 示例 | 备注 |
-|------|------|------|------|------|
-| **REQ-ID** | 需求编号 | ✅ | `REQ-123` | 必须唯一，格式为 REQ-NNN |
-| **功能标题** | 简短功能描述 | ✅ | `用户认证功能` | 用于 Git 分支命名和文档标题 |
-| **计划URLs** | 外部参考链接 | ❌ | `https://docs.example.com/auth` | 可选，多个 URL 用 `\|` 分隔 |
-
-## 🎬 使用场景
-
-### ✅ 推荐场景
-
-| 场景 | 说明 |
-|------|------|
-| 启动全新功能开发 | 从零开始的新功能需求 |
-| 首次创建需求文档 | 需要生成 PRD、EPIC、TASKS 等完整文档 |
-| 长期项目启动 | 持续时间超过 1 周的项目 |
-
-### ❌ 不推荐场景
-
-| 场景 | 替代方案 |
-|------|----------|
-| 恢复中断的开发 | 使用 `/flow-restart "REQ-123"` |
-| 修复 Bug | 使用 `/flow-fix "BUG-001\|描述"` |
-| 仅初始化目录结构 | 使用 `/flow-init "REQ-123\|标题"` |
-| 快速原型验证 | 使用 `/flow-ideate "想法描述"` |
-
-## 🔄 执行流程
-
-```text
-/flow-new "REQ-123|用户认证|https://docs.example.com/auth"
-  ↓
-Stage 1: 初始化 (flow-init)
-  ├─ 创建需求目录结构
-  ├─ 加载路线图和架构上下文（如果存在）
-  ├─ 创建 Git 分支 feature/REQ-123-user-auth
-  └─ 初始化 orchestration_status.json
-  ↓
-Stage 2: PRD 生成 (prd-writer 代理)
-  ├─ 分析外部参考链接
-  ├─ 研究现有代码库
-  ├─ 使用 PRD_TEMPLATE 生成 PRD.md
-  └─ 记录到 EXECUTION_LOG.md
-  ↓
-Stage 3: UI 原型生成 (ui-designer 代理，条件触发)
-  ├─ 检测 PRD 中是否有 UI 需求
-  ├─ 如有 UI 需求，生成 UI_PROTOTYPE.html
-  ├─ 响应式设计（320px/768px/1024px）
-  └─ 完整交互状态和真实图片
-  ↓
-Stage 4: 技术设计 (tech-architect 代理)
-  ├─ 分析 PRD + 现有代码库
-  ├─ 设计技术方案（避免过度设计）
-  ├─ 生成 TECH_DESIGN.md
-  └─ Anti-Tech-Creep 强制执行
-  ↓
-Stage 4.5: 需求质量检查 (checklist-agent，可选) ⭐ 新增
-  ├─ 生成类型特定检查清单 (ux, api, security 等)
-  ├─ 验证 5 个质量维度
-  ├─ 计算完成百分比
-  └─ 80% 门禁阈值（进入 EPIC 前）
-  ↓
-Stage 5: EPIC & TASKS 生成 (planner 代理)
-  ├─ 分析 PRD + TECH_DESIGN
-  ├─ 使用 EPIC_TEMPLATE 生成 EPIC.md
-  ├─ 使用 TASKS_TEMPLATE 生成 TASKS.md
-  └─ 任务按 TDD 顺序排列（Phase 1-5）
-  ↓
-Stage 6: 开发 (dev-implementer 代理 + 主代理执行)
-  ├─ dev-implementer 生成 IMPLEMENTATION_PLAN.md
-  ├─ 主代理执行代码实现
-  ├─ 遵循 TDD：先测试后实现
-  └─ 实时更新 TASKS.md 进度
-  ↓
-Stage 7: QA (qa-tester 代理)
-  ├─ 生成 TEST_PLAN.md
-  ├─ 执行测试（单元测试、集成测试）
-  ├─ 生成 TEST_REPORT.md
-  └─ 安全扫描（security-reviewer 代理）
-  ↓
-Stage 8: Release (release-manager 代理)
-  ├─ 生成 RELEASE_PLAN.md
-  ├─ 检查发布准备度
-  ├─ 创建 Pull Request
-  └─ 创建 Git Tag（可选）
-```
-
-## 💡 示例
-
-### 示例 1: 基础用法
-
-```bash
-/flow-new "REQ-001|用户登录功能"
-```
-
-**输出**:
-```
-devflow/requirements/REQ-001/
-├── orchestration_status.json
-├── EXECUTION_LOG.md
-├── PRD.md
-├── EPIC.md
-├── TASKS.md
-└── ... (其他文档)
-```
-
-**Git 分支**: `feature/REQ-001-user-login`
-
-### 示例 2: 带外部参考
-
-```bash
-/flow-new "REQ-002|支付集成|https://stripe.com/docs/api"
-```
-
-**效果**:
-- PRD 中会引用 Stripe API 文档
-- 技术设计会考虑 Stripe 集成方案
-- 任务分解会包含 Stripe SDK 集成任务
-
-### 示例 3: 多个参考链接
-
-```bash
-/flow-new "REQ-003|数据分析|https://doc1.com|https://doc2.com"
-```
-
-**效果**:
-- 系统会抓取两个外部链接内容
-- PRD 中会综合参考两份文档
-- `research/` 目录会保存抓取的内容
-
-## 📂 输出文件结构
-
-执行 `/flow-new` 后会生成完整的需求目录：
-
-```
-devflow/requirements/REQ-XXX/
-├── orchestration_status.json    # 状态管理（阶段、进度、时间戳）
-├── EXECUTION_LOG.md             # 完整审计轨迹
-├── PRD.md                       # 产品需求文档
-├── UI_PROTOTYPE.html            # UI 原型（条件生成）
-├── TECH_DESIGN.md               # 技术设计文档
-├── checklists/                  # 需求质量检查清单 ⭐ 新增
-│   ├── ux.md                    # UX 检查清单
-│   ├── api.md                   # API 检查清单
-│   └── security.md              # Security 检查清单
-├── EPIC.md                      # Epic 规划和分解
-├── TASKS.md                     # 单一统一任务列表
-├── tasks/                       # 任务执行产物
-│   ├── TASK_001.completed
-│   ├── TASK_002.completed
-│   └── IMPLEMENTATION_PLAN.md
-├── research/                    # 外部研究材料（MCP 抓取）
-├── TEST_PLAN.md                 # QA 测试策略
-├── TEST_REPORT.md               # QA 测试结果
-├── SECURITY_PLAN.md             # 安全审查计划
-├── SECURITY_REPORT.md           # 安全扫描结果
-└── RELEASE_PLAN.md              # 发布 checklist
-```
-
-## 🔗 相关命令
-
-- [`/flow-init`](./flow-init.md) - 仅初始化需求结构（不执行后续阶段）
-- [`/flow-checklist`](../../.claude/commands/flow-checklist.md) - 需求质量检查（EPIC 前 80% 门禁）⭐ 新增
-- [`/flow-restart`](./flow-restart.md) - 恢复中断的开发
-- [`/flow-status`](./flow-status.md) - 查看需求开发进度
-- [`/flow-verify`](./flow-verify.md) - 验证文档一致性
-- [`/flow-fix`](./flow-fix.md) - Bug 修复工作流（替代 flow-new）
-
-## ⚙️ 配置选项
-
-### 环境变量
+请使用显式的 5 阶段主链：
 
 ```bash
-# 质量闸配置
-export MIN_TEST_COVERAGE=80              # 最小测试覆盖率
-export STRICT_TYPE_CHECKING=true         # 严格类型检查
-
-# 流程控制
-export FLOW_AUTO_APPROVE=false           # 质量闸是否需要手动批准
-export FLOW_SKIP_BACKGROUND=false        # 是否跳过后台进程启动
-
-# MCP 集成
-export WEBFETCH_TIMEOUT=30               # 外部链接抓取超时（秒）
-export ALLOWED_DOMAINS=""                # 允许抓取的域名白名单
+/flow:init "REQ-123|功能标题|https://plan.example.com"
+/flow:spec "REQ-123"
+/flow:dev "REQ-123"
+/flow:verify "REQ-123" --strict
+/flow:release "REQ-123"
 ```
 
-### Hooks 配置
-
-`.claude/settings.json` 中的 Hooks 会在 flow-new 执行过程中触发：
-
-- **PreToolUse**: 阻止不合规操作（如违反 TDD 顺序）
-- **PostToolUse**: 自动记录文件变更到 EXECUTION_LOG.md
-- **Constitution Compliance**: 每个阶段强制执行 Constitution v2.0.0
-
-## 🚨 常见问题
-
-### Q1: flow-new 执行到一半中断了怎么办？
-
-**A**: 使用 `/flow-restart "REQ-123"` 自动检测重启点并继续执行。
+## 废弃原因
 
-### Q2: 如何跳过某些阶段（如 UI 原型）？
+- 一键黑盒执行不利于中断恢复。
+- 长时运行时阶段边界不清晰。
+- 质量闸与恢复策略已统一到 `/flow:verify` 与 `/flow:dev --resume`。
 
-**A**: UI 原型是条件触发的。如果 PRD 中没有 UI 需求，会自动跳过。其他阶段暂不支持跳过。
-
-### Q3: 外部链接抓取失败怎么办？
-
-**A**:
-1. 检查网络连接
-2. 检查 `ALLOWED_DOMAINS` 配置
-3. 增加 `WEBFETCH_TIMEOUT` 超时时间
-4. 手动将参考内容保存到 `research/` 目录
-
-### Q4: 生成的 PRD 不符合预期？
-
-**A**:
-1. 提供更详细的外部参考链接
-2. 执行后手动编辑 PRD.md
-3. 使用 `/flow-restart "REQ-123" --from=prd` 重新生成
-
-### Q5: 任务顺序不符合 TDD 要求？
-
-**A**: 这是 Bug。TASKS.md 必须按照 Phase 1-5 TDD 顺序排列：
-- Phase 1: 测试基础设施
-- Phase 2: 单元测试编写
-- Phase 3: 集成测试编写
-- **Phase 3.5: TEST VERIFICATION CHECKPOINT** (阻塞点)
-- Phase 4: 功能实现
-- Phase 5: 文档和清理
-
-如果发现顺序错误，请报告 Bug。
-
-## 📊 性能预估
-
-| 需求复杂度 | 预估执行时间 | 生成文件数 | Token 消耗 |
-|-----------|-------------|-----------|-----------|
-| 简单（CRUD） | 5-10 分钟 | 10-15 个 | ~20K tokens |
-| 中等（API 集成） | 15-30 分钟 | 15-20 个 | ~50K tokens |
-| 复杂（多模块） | 30-60 分钟 | 20-30 个 | ~100K tokens |
-
-**注**: 实际时间取决于代码库大小、外部链接数量、代理响应速度等因素。
-
-## 🔍 调试模式
-
-启用详细日志查看执行细节：
-
-```bash
-export FLOW_DEBUG=1
-/flow-new "REQ-123|测试功能"
-```
+## 旧命令映射
 
-日志文件位置：`.claude/logs/flow-*.log`
+| 旧命令 | 新命令 |
+|--------|--------|
+| `/flow-new` | `/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release` |
+| `/flow-restart` | `/flow:dev --resume` 或结合 `/flow:status` 恢复 |
+| `/flow-quality` | `/flow:verify` |
 
-## 📚 深度阅读
+## 相关命令
 
-- [执行模型详解](../architecture/execution-model.md)
-- [子代理工作流](../architecture/agent-workflow.md)
-- [质量闸系统](../architecture/quality-gates.md)
-- [Constitution v2.0.0](../architecture/constitution.md)
+- [`/flow:init`](./flow-init.zh-CN.md)
+- [`/flow:spec`](../../.claude/commands/flow/spec.md)
+- [`/flow:dev`](../../.claude/commands/flow/dev.md)
+- [`/flow:verify`](../../.claude/commands/flow/verify.md)
+- [`/flow:release`](../../.claude/commands/flow/release.md)

package/docs/guides/getting-started.md

@@ -48,32 +48,33 @@ This script will check:
 
 ## 🎯 Your First Requirement
 
-### Step 1: Start Development Flow
+### Step 1: Run the Mainline Flow
 
 ```bash
-/flow-new "REQ-001|User Authentication|https://docs.example.com/auth"
+/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"
 ```
 
 This will:
-1. Initialize requirement structure
-2. Generate PRD
-3. Generate UI prototype (if needed)
-4. Create technical design
-5. Generate EPIC and TASKS
-6. Execute development
-7. Run QA tests
-8. Prepare release
+1. Initialize requirement context package
+2. Generate executable task-manifest
+3. Dispatch task execution with checkpoints
+4. Run quick/strict quality gates
+5. Generate release note and cleanup runtime logs
 
 ### Step 2: Check Progress
 
 ```bash
-/flow-status REQ-001
+/flow:status REQ-001
 ```
 
 ### Step 3: Resume If Interrupted
 
 ```bash
-/flow-restart "REQ-001"
+/flow:dev "REQ-001" --resume
 ```
 
 ## 🛠️ Core Scripts
@@ -184,8 +185,8 @@ VERBOSE=true bash .claude/tests/run-all-tests.sh --scripts
 
 ## 💡 Tips
 
-1. **Always check progress** with `/flow-status` before continuing work
-2. **Use `/flow-verify`** to check document consistency
+1. **Always check progress** with `/flow:status` before continuing work
+2. **Use `/flow:verify`** to check quality gates and consistency
 3. **Enable debug mode** if you encounter issues: `export FLOW_DEBUG=1`
 4. **Read the Constitution** to understand quality standards
 
@@ -200,5 +201,5 @@ VERBOSE=true bash .claude/tests/run-all-tests.sh --scripts
 **Ready to start? Run your first command:**
 
 ```bash
-/flow-new "REQ-001|My First Feature"
+/flow:init "REQ-001|My First Feature"
 ```