cc-devflow 4.2.0 → 4.4.1

package/docs/commands/flow-init.md

@@ -1,140 +0,0 @@
-# `/flow:init` - Initialize Requirement Structure
-
-[中文文档](./flow-init.zh-CN.md) | [English](./flow-init.md)
-
----
-
-## 📋 Overview
-
-Initialize requirement directory structure and package runtime context. This is stage 1 of the canonical mainline (`/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release`) and can also be used independently.
-
-## 🎯 Syntax
-
-```bash
-/flow:init "REQ-ID|Feature Title"
-# or
-/flow:init --interactive
-```
-
-## 📖 Parameters
-
-| Parameter | Description | Required | Example |
-|-----------|-------------|----------|---------|
-| **REQ-ID** | Requirement number | ✅ | `REQ-123` |
-| **Feature Title** | Brief description | ✅ | `User Authentication Feature` |
-
-> If the title contains non-ASCII text, the agent produces an English semantic translation for branch naming (not pinyin), while keeping the original title in docs.
-| **--interactive** | Interactive ID selection | ❌ | Auto-select next available ID |
-
-## 🎬 Use Cases
-
-### ✅ Recommended Scenarios
-- Initialize requirement structure alone
-- Have roadmap, need to locate requirement
-- Need to manually create document content
-
-### ❌ Not Recommended Scenarios
-- Expecting full delivery with one command (deprecated `/flow:new`)
-- Resume development → Use `/flow:restart`
-
-## 🔄 Execution Flow (includes Stage 1.5)
-
-```text
-/flow:init "REQ-123|User Authentication Feature"
-  ↓
-Stage 1: Prerequisites validation
-  ├─ Check Git repository
-  ├─ Check devflow/ directory
-  └─ Verify REQ-ID uniqueness
-  ↓
-Stage 1.2: Git branch creation
-  └─ Create feature/REQ-XXX-english-slug branch (model-translated, not pinyin)
-  ↓
-Stage 1.5: Roadmap & Architecture context loading (NEW)
-  ├─ Check ROADMAP.md existence
-  ├─ Locate requirement in roadmap
-  │  ├─ RM-ID (Roadmap Item ID)
-  │  ├─ Milestone (M{n}-Q{q}-{yyyy})
-  │  └─ Cluster (Feature cluster)
-  ├─ Load ARCHITECTURE.md
-  └─ Display architecture context
-     ├─ Feature Architecture (feature layers)
-     ├─ Technical Architecture (tech stack)
-     └─ Module Structure (target modules)
-  ↓
-Stage 2: Directory structure creation
-  ├─ Create devflow/requirements/REQ-XXX/
-  ├─ Initialize orchestration_status.json
-  └─ Create EXECUTION_LOG.md
-  ↓
-Stage 2.3: Brainstorming (skill)
-  └─ Generate devflow/requirements/REQ-XXX/BRAINSTORM.md as the “North Star”
-  ↓
-Stage 2.5: Research (subagent, mandatory, context-isolated)
-  ├─ Run internal codebase research → research/internal/codebase-overview.md
-  ├─ Capture external sources into files → research/mcp/YYYYMMDD/**
-  ├─ Produce decisions → research/research-summary.md
-  ├─ Fill tasks → research/tasks.json (decision/rationale/alternatives)
-  └─ Consolidate → research/research.md (validated; no TODO/PLACEHOLDER)
-```
-
-## 💡 Examples
-
-### Example 1: Basic Usage
-
-```bash
-/flow:init "REQ-123|User Authentication Feature"
-```
-
-### Example 2: Interactive Mode
-
-```bash
-/flow:init --interactive
-# System will auto-select next available ID
-```
-
-### Example 3: Output with Roadmap Context
-
-```
-===================================================================
-📍 Requirement Location in Roadmap
-===================================================================
-
-📋 Requirement:    REQ-123
-🎯 Roadmap Item:   RM-05
-📝 Feature:        User Management
-📌 Derived From:   Product Backlog
-
-📅 Timeline:
-   Quarter:        Q2 2025
-   Milestone:      M2-Q2-2025
-   Cluster:        Core Features
-===================================================================
-
-🏗️  Architecture Context
-===================================================================
-
-🎯 Feature Architecture:
-   Layer: Core (Core Feature Layer)
-   Related Features: Authentication, Authorization
-
-🔧 Technical Architecture:
-   Tech Stack Layer: Business Logic + Data Access
-   Key Technologies: Node.js, PostgreSQL, Redis
-
-📦 Module Structure:
-   Target Modules: src/auth/, src/user/
-===================================================================
-```
-
-## 📂 Output
-
-- `devflow/requirements/REQ-XXX/` initialized directory (includes `BRAINSTORM.md` + `research/`)
-- `orchestration_status.json` + `EXECUTION_LOG.md`
-- Roadmap and architecture context display (if exists)
-
-## 🔗 Related Commands
-
-- [`/core-roadmap`](./core-roadmap.md) - Generate roadmap first
-- [`/core-architecture`](./core-architecture.md) - Generate architecture first
-- Canonical chain: `/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`

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

@@ -1,169 +0,0 @@
-# `/flow:init` - 初始化需求结构
-
-## 📋 概述
-
-初始化需求目录结构并打包运行时上下文。这是当前主链（`/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release`）的第 1 阶段，也可以单独使用。
-
-## 🎯 语法
-
-```bash
-/flow:init "REQ-ID|功能标题"
-# 或
-/flow:init --interactive
-```
-
-## 📖 参数详解
-
-| 参数 | 说明 | 必填 | 示例 |
-|------|------|------|------|
-| **REQ-ID** | 需求编号 | ✅ | `REQ-123` |
-| **功能标题** | 简短描述 | ✅ | `用户认证功能` |
-| **--interactive** | 交互式选择 ID | ❌ | 自动选择下一个可用 ID |
-
-> 若标题包含中文/非ASCII，分支名将使用模型意译生成英文语义短语（禁止拼音/音译），文档标题仍保留原始中文。
-
-## 🎬 使用场景
-
-### ✅ 推荐场景
-- 单独初始化需求结构
-- 已有路线图，需要定位需求
-- 需要手动创建文档内容
-
-### ❌ 不推荐场景
-- 期望单命令完成交付（旧 `/flow:new` 已废弃）
-- 恢复开发 → 使用 `/flow:restart`
-
-## 🔄 执行流程
-
-```text
-/flow:init "REQ-123|用户认证功能"
-  ↓
-Stage 1: 前置条件验证
-  ├─ 检查 Git 仓库
-  ├─ 检查 devflow/ 目录
-  └─ 验证 REQ-ID 唯一性
-  ↓
-Stage 1.2: Git 分支创建
-  └─ 创建 feature/REQ-XXX-english-slug 分支（标题英文意译，非拼音）
-  ↓
-Stage 1.5: 路线图与架构上下文加载（NEW）
-  ├─ 检查 ROADMAP.md 存在性
-  ├─ 定位需求在路线图中的位置
-  │  ├─ RM-ID (Roadmap Item ID)
-  │  ├─ Milestone (M{n}-Q{q}-{yyyy})
-  │  └─ Cluster (功能群组)
-  ├─ 加载 ARCHITECTURE.md
-  └─ 显示架构上下文
-     ├─ Feature Architecture (功能分层)
-     ├─ Technical Architecture (技术栈)
-     └─ Module Structure (目标模块)
-  ↓
-Stage 2: 目录结构创建
-  ├─ 创建 devflow/requirements/REQ-123/
-  ├─ 创建子目录 research/
-  ├─ 初始化 orchestration_status.json
-  └─ 初始化 EXECUTION_LOG.md
-  ↓
-Stage 2.3: 头脑风暴（skill）
-  └─ 生成 devflow/requirements/REQ-XXX/BRAINSTORM.md 作为需求「北极星」
-  ↓
-Stage 2.5: 调研（subagent，默认必跑，上下文隔离）
-  ├─ 内部代码库调研 → research/internal/codebase-overview.md
-  ├─ 外部资料落盘 → research/mcp/YYYYMMDD/**
-  ├─ 决策摘要 → research/research-summary.md
-  ├─ 任务回填 → research/tasks.json（decision/rationale/alternatives 完整）
-  └─ 研究整合 → research/research.md（通过校验，无 TODO/PLACEHOLDER）
-```
-
-## 💡 示例
-
-### 示例 1: 基础用法
-
-```bash
-/flow:init "REQ-123|用户认证功能"
-```
-
-**输出示例（带路线图上下文）**:
-
-```text
-===================================================================
-📍 Requirement Location in Roadmap
-===================================================================
-
-📋 Requirement:    REQ-123
-🎯 Roadmap Item:   RM-05
-📝 Feature:        User Management
-📌 Derived From:   Product Backlog
-
-📅 Timeline:
-   Quarter:        Q2 2025
-   Milestone:      M2-Q2-2025
-   Cluster:        Core Features
-===================================================================
-
-🏗️  Architecture Context
-===================================================================
-
-🎯 Feature Architecture:
-   Layer: Core (核心功能层)
-   Related Features: Authentication, Authorization
-
-🔧 Technical Architecture:
-   Tech Stack Layer: Business Logic + Data Access
-   Key Technologies: Node.js, PostgreSQL, Redis
-
-📦 Module Structure:
-   Target Modules: src/auth/, src/user/
-===================================================================
-```
-
-### 示例 2: 交互式模式
-
-```bash
-/flow:init --interactive
-```
-
-**效果**:
-- 自动扫描现有需求编号
-- 提示下一个可用 ID（如 REQ-124）
-- 引导输入功能标题
-
-## 📂 输出文件结构
-
-```
-devflow/requirements/REQ-123/
-├── orchestration_status.json    # 状态管理
-├── EXECUTION_LOG.md             # 审计轨迹
-├── research/                    # 研究材料目录
-└── (等待后续阶段生成其他文档)
-```
-
-## 🔗 相关命令
-
-- 主链命令：`/flow:init` → `/flow:spec` → `/flow:dev` → `/flow:verify` → `/flow:release`
-- [`/core-roadmap`](./core-roadmap.md) - 先生成路线图
-- [`/core-architecture`](./core-architecture.md) - 先生成架构
-- [`/flow:status`](../../.claude/commands/flow/status.md) - 查看进度
-
-## 🚨 常见问题
-
-### Q: Stage 1.5 没有加载路线图上下文？
-
-**A**: 检查以下条件：
-1. `devflow/ROADMAP.md` 文件是否存在
-2. ROADMAP.md 中是否有对应的 RM-ID 映射
-3. 使用 `/core-roadmap` 先生成路线图
-
-### Q: 如何手动定位需求到路线图？
-
-**A**: 编辑 `devflow/ROADMAP.md`，在 Implementation Tracking 表格中添加映射：
-
-```markdown
-| RM-05 | User Management | ... | REQ-123 | ... |
-```
-
-## 📚 深度阅读
-
-- [路线图系统](../guides/roadmap-guide.md)
-- [架构上下文加载](../architecture/context-loading.md)
-- [目录结构规范](../architecture/directory-structure.md)

package/docs/commands/flow-new.md

@@ -1,39 +0,0 @@
-# `/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.
-
-## Canonical Mainline
-
-Use the explicit 5-stage chain:
-
-```bash
-/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"
-```
-
-## Why `/flow-new` Is Deprecated
-
-- 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`.
-
-## Legacy to Current Mapping
-
-| 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` |
-
-## Related Commands
-
-- [`/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,39 +0,0 @@
-# `/flow-new` - 已废弃别名
-
-[English](./flow-new.md) | [中文文档](./flow-new.zh-CN.md)
-
-`/flow-new` 仅为兼容保留，不再作为主流程入口。
-
-## 当前主链
-
-请使用显式的 5 阶段主链：
-
-```bash
-/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"
-```
-
-## 废弃原因
-
-- 一键黑盒执行不利于中断恢复。
-- 长时运行时阶段边界不清晰。
-- 质量闸与恢复策略已统一到 `/flow:verify` 与 `/flow:dev --resume`。
-
-## 旧命令映射
-
-| 旧命令 | 新命令 |
-|--------|--------|
-| `/flow-new` | `/flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release` |
-| `/flow-restart` | `/flow:dev --resume` 或结合 `/flow:status` 恢复 |
-| `/flow-quality` | `/flow:verify` |
-
-## 相关命令
-
-- [`/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/lib/compiler/__tests__/compile-regression.test.js

@@ -1,103 +0,0 @@
-/**
- * T043: Compile Regression Tests
- *
- * [INPUT]: 临时 .claude 项目
- * [OUTPUT]: compile() 端到端回归验证
- * [POS]: 修复 adapt 回归，确保命令与技能正确落盘
- * [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
- */
-
-const fs = require('fs');
-const path = require('path');
-const os = require('os');
-
-const { compile } = require('../index.js');
-
-function writeFile(filePath, content) {
-  fs.mkdirSync(path.dirname(filePath), { recursive: true });
-  fs.writeFileSync(filePath, content);
-}
-
-function setupProjectFixture(rootDir) {
-  writeFile(path.join(rootDir, '.claude/commands/flow/new.md'), `---
-name: flow-new
-description: Create new requirement
----
-# Flow New
-
-Run flow new
-`);
-
-  writeFile(path.join(rootDir, '.claude/skills/workflow/flow-dev/SKILL.md'), `---
-name: flow-dev
-description: Workflow dev skill
----
-# flow-dev
-`);
-
-  writeFile(path.join(rootDir, '.claude/skills/orchestrator/SKILL.md'), `---
-name: orchestrator
-description: Root level skill
----
-# orchestrator
-`);
-
-  writeFile(path.join(rootDir, '.claude/agents/planner.md'), `---
-name: planner
-description: Plan tasks
----
-# planner
-`);
-
-  writeFile(path.join(rootDir, '.claude/rules/base-rule.md'), `---
-description: Base rule
-alwaysApply: true
----
-# rule
-`);
-}
-
-describe('compile() regression', () => {
-  let tempDir;
-  let originalCwd;
-
-  beforeEach(() => {
-    tempDir = fs.mkdtempSync(path.join(os.tmpdir(), 'compile-regression-'));
-    setupProjectFixture(tempDir);
-    originalCwd = process.cwd();
-    process.chdir(tempDir);
-  });
-
-  afterEach(() => {
-    process.chdir(originalCwd);
-    fs.rmSync(tempDir, { recursive: true, force: true });
-  });
-
-  test('should compile nested commands and emit skills for codex', async () => {
-    fs.writeFileSync('AGENTS.md', '# User Memory\n\nKeep this content.\n');
-
-    const result = await compile({
-      sourceDir: '.claude/commands',
-      skillsDir: '.claude/skills',
-      outputBaseDir: '.',
-      platforms: ['codex'],
-      verbose: false
-    });
-
-    expect(result.success).toBe(true);
-    expect(result.filesCompiled).toBe(1);
-    expect(result.skillsRegistered).toBe(2);
-    expect(result.skillsEmitted).toBe(2);
-    expect(fs.existsSync('.codex/prompts/flow/new.md')).toBe(true);
-    expect(fs.existsSync('.codex/skills/flow-dev/SKILL.md')).toBe(true);
-    expect(fs.existsSync('.codex/skills/orchestrator/SKILL.md')).toBe(true);
-    expect(fs.existsSync('AGENTS.md')).toBe(true);
-
-    const agentsContent = fs.readFileSync('AGENTS.md', 'utf8');
-    expect(agentsContent).toContain('# User Memory');
-    expect(agentsContent).toContain('<!-- cc-devflow:codex-agents:start -->');
-    expect(agentsContent).toContain('<!-- cc-devflow:codex-rules:start -->');
-    expect(agentsContent).not.toContain('# planner');
-    expect(agentsContent).not.toContain('# rule');
-  });
-});