cc-devflow 4.2.0 → 4.4.1

package/.claude/skills/workflow/flow-verify/SKILL.md

@@ -1,53 +0,0 @@
----
-name: flow-verify
-description: 'Run layered quick/strict gates and emit report-card for a requirement. Use before release and after major dev changes.'
----
-
-# Flow-Verify Skill
-
-> [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
-
-## Purpose
-
-执行质量门禁并输出 `report-card.json`，作为发布前唯一准入依据。
-
-## Input Format
-
-```bash
-/flow:verify "REQ_ID" [--strict] [--skip-review]
-```
-
-## Execution Steps
-
-1. 解析参数。
-2. 调用验证引擎：
-
-```bash
-npm run harness:verify -- --change-id "${REQ_ID}" [--strict] [--skip-review]
-```
-
-3. 读取并检查输出：
-   - `devflow/requirements/${REQ_ID}/report-card.json`
-   - `overall == "pass"` 才能进入 release
-
-## Gate Model
-
-- Quick Gate（默认）:
-  - lint
-  - typecheck
-  - test
-- Strict Gate（`--strict`）:
-  - test:integration（如存在）
-  - npm audit
-  - codex review（可 `--skip-review`）
-
-## Exit Criteria
-
-- `report-card.json` 生成成功
-- 若 `overall=fail`，停止发布并修复失败项
-
-## Next Step
-
-```bash
-/flow:release "${REQ_ID}"
-```

package/.claude/skills/workflow/flow-verify/context.jsonl

@@ -1,5 +0,0 @@
-{"file": "devflow/requirements/{REQ}/task-manifest.json", "reason": "Task status baseline"}
-{"file": "devflow/requirements/{REQ}/report-card.json", "reason": "Previous verification result", "optional": true}
-{"file": "devflow/requirements/{REQ}/harness-state.json", "reason": "Lifecycle status", "optional": true}
-{"file": "devflow/requirements/{REQ}/context-package.md", "reason": "Constraints and next commands", "optional": true}
-{"file": ".claude/rules/project-constitution.md", "reason": "Quality rules and constraints"}

package/.claude/skills/workflow.yaml

@@ -1,219 +0,0 @@
-# =============================================================================
-# CC-DevFlow Workflow Schema v6.0.0 (Harness-First)
-# =============================================================================
-# [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
-# =============================================================================
-
-name: cc-devflow
-version: "6.0.0"
-description: CC-DevFlow Harness-First workflow schema
-
-# =============================================================================
-# 工件定义 (Artifacts)
-# =============================================================================
-# 主链：init -> spec -> dev -> verify -> release
-# 产物最小集：context-package / task-manifest / report-card / release-note
-
-artifacts:
-  - id: context_package
-    generates: devflow/requirements/{REQ}/context-package.md
-    requires: []
-    skill: flow-init
-    instruction: |
-      初始化需求并生成上下文包。
-
-  - id: harness_state
-    generates: devflow/requirements/{REQ}/harness-state.json
-    requires: [context_package]
-    skill: flow-init
-    instruction: |
-      记录 requirement 生命周期状态。
-
-  - id: task_manifest
-    generates: devflow/requirements/{REQ}/task-manifest.json
-    requires: [context_package]
-    skill: flow-spec
-    instruction: |
-      生成依赖可执行的任务清单。
-
-  - id: runtime_events
-    generates: .harness/runtime/{REQ}/**
-    requires: [task_manifest]
-    skill: flow-dev
-    glob: true
-    optional: true
-    instruction: |
-      执行任务并写入 checkpoint/events。
-
-  - id: report_card
-    generates: devflow/requirements/{REQ}/report-card.json
-    requires: [task_manifest]
-    skill: flow-verify
-    instruction: |
-      执行 quick/strict 质量门禁并产出报告卡。
-
-  - id: release_note
-    generates: devflow/requirements/{REQ}/RELEASE_NOTE.md
-    requires: [report_card]
-    skill: flow-release
-    optional: true
-    instruction: |
-      发布通过后生成发布说明。
-
-  - id: bug_analysis
-    generates: devflow/bugs/{BUG}/ANALYSIS.md
-    requires: []
-    skill: flow-fix
-    optional: true
-    instruction: |
-      分析 Bug 根因并沉淀修复输入。
-
-  - id: bug_plan
-    generates: devflow/bugs/{BUG}/PLAN.md
-    requires: [bug_analysis]
-    skill: flow-fix
-    optional: true
-    instruction: |
-      生成 Bug 修复计划。
-
-# =============================================================================
-# 状态检测配置
-# =============================================================================
-detection:
-  method: file_existence
-  fallback: harness-state.json
-  glob_options:
-    ignore:
-      - "**/.DS_Store"
-      - "**/*.bak"
-      - "**/node_modules/**"
-
-# =============================================================================
-# Skill 分类定义
-# =============================================================================
-# 仅登记仓库内实际存在的 skill 目录
-
-skills:
-  workflow:
-    - id: flow-init
-      path: workflow/flow-init
-      description: 主链初始化 (context-package + harness-state)
-    - id: flow-spec
-      path: workflow/flow-spec
-      description: 主链规格阶段 (task-manifest)
-    - id: flow-dev
-      path: workflow/flow-dev
-      description: 主链开发执行 (dispatch/resume)
-    - id: flow-verify
-      path: workflow/flow-verify
-      description: 主链质量门禁 (report-card)
-    - id: flow-release
-      path: workflow/flow-release
-      description: 主链发布收尾 (release/janitor)
-    - id: flow-quality
-      path: workflow/flow-quality
-      description: 旧质量流程 (deprecated)
-    - id: flow-fix
-      path: workflow/flow-fix
-      description: Bug 修复
-
-  domain:
-    - id: tdd
-      path: domain/tdd
-      description: TDD Iron Law 执行
-    - id: debugging
-      path: domain/debugging
-      description: 系统化调试
-    - id: brainstorming
-      path: domain/brainstorming
-      description: 需求头脑风暴
-    - id: attention-refresh
-      path: domain/attention-refresh
-      description: 注意力刷新协议
-    - id: verification
-      path: domain/verification
-      description: 完成前验证
-    - id: receiving-review
-      path: domain/receiving-review
-      description: 处理代码审查反馈
-    - id: finishing-branch
-      path: domain/finishing-branch
-      description: 分支完成决策
-
-  guardrail:
-    - id: constitution-guardian
-      path: guardrail/constitution-guardian
-      description: Constitution 合规检查
-    - id: tdd-enforcer
-      path: guardrail/tdd-enforcer
-      description: TDD 顺序强制执行
-
-  utility:
-    - id: npm-release
-      path: utility/npm-release
-      description: NPM 包发布
-    - id: fractal-docs
-      path: utility/fractal-docs
-      description: 分形文档生成
-    - id: journey-checker
-      path: utility/journey-checker
-      description: 跨需求一致性检查
-    - id: skill-creator
-      path: utility/skill-creator
-      description: Skill 创建向导
-    - id: file-standards
-      path: utility/file-standards
-      description: 文件命名规范
-    - id: constitution-quick-ref
-      path: utility/constitution-quick-ref
-      description: Constitution 快速参考
-
-# =============================================================================
-# 上下文注入配置
-# =============================================================================
-context:
-  global:
-    - file: .claude/rules/project-constitution.md
-      reason: Quality rules and constraints
-
-  defaults:
-    workflow:
-      - file: devflow/requirements/{REQ}/context-package.md
-        reason: Execution context package
-        optional: true
-      - file: devflow/requirements/{REQ}/task-manifest.json
-        reason: Executable task graph
-        optional: true
-    domain:
-      - file: devflow/requirements/{REQ}/task-manifest.json
-        reason: Current task context
-        optional: true
-
-# =============================================================================
-# 废弃命令/技能映射
-# =============================================================================
-deprecated:
-  - id: flow-new
-    replacement: flow-init
-    message: "Use /flow:init -> /flow:spec -> /flow:dev -> /flow:verify -> /flow:release"
-  - id: flow-clarify
-    replacement: flow-spec
-    message: "Clarification stage removed from default chain"
-  - id: flow-checklist
-    replacement: flow-verify
-    message: "Checklist stage merged into verification gates"
-  - id: flow-quality
-    replacement: flow-verify
-    message: "Use /flow:verify for quick/strict gates"
-  - id: flow-prd
-    replacement: flow-spec
-    message: "Use /flow:spec instead"
-  - id: flow-tech
-    replacement: flow-spec
-    message: "Use /flow:spec instead"
-  - id: flow-ui
-    replacement: flow-spec
-    message: "Use /flow:spec instead"
-  - id: flow-epic
-    replacement: flow-spec
-    message: "Use /flow:spec instead"

package/.claude/tests/README.md

@@ -1,300 +0,0 @@
-# CC-DevFlow 测试套件
-
-## 目录结构
-
-```text
-tests/
-├── README.md              # 本文档
-├── test-framework.sh      # 测试框架 (断言、mock、报告)
-├── run-all-tests.sh       # 运行所有测试
-├── scripts/               # 脚本单元测试
-│   ├── test_common.sh
-│   ├── test_check_prerequisites.sh
-│   ├── test_setup_epic.sh
-│   ├── test_mark_task_complete.sh
-│   ├── test_check_task_status.sh
-│   ├── test_validate_constitution.sh
-│   └── test_generate_status_report.sh
-├── commands/              # 命令集成测试
-│   ├── test_flow_init.sh
-│   ├── test_flow_prd.sh
-│   ├── test_flow_epic.sh
-│   ├── test_flow_dev.sh
-│   ├── test_flow_qa.sh
-│   └── test_flow_release.sh
-├── e2e/                   # 端到端测试
-│   ├── test_full_workflow.sh
-│   ├── test_interruption_recovery.sh
-│   └── test_quality_gates.sh
-└── fixtures/              # 测试数据和 mock
-    ├── mock_requirements/
-    ├── mock_git/
-    └── test_data/
-```
-
-## 测试框架
-
-### 核心功能
-
-- **断言函数**: assert_equals, assert_contains, assert_file_exists, assert_json_valid
-- **Mock 系统**: mock_git, mock_file_system, mock_web_fetch
-- **测试隔离**: 每个测试使用独立的临时目录
-- **报告生成**: 统计通过/失败数量，生成详细报告
-
-### 运行测试
-
-```bash
-# 运行所有测试
-.claude/tests/run-all-tests.sh
-
-# 运行脚本测试
-.claude/tests/run-all-tests.sh --scripts
-
-# 运行命令测试
-.claude/tests/run-all-tests.sh --commands
-
-# 运行端到端测试
-.claude/tests/run-all-tests.sh --e2e
-
-# 运行特定测试
-.claude/tests/scripts/test_common.sh
-
-# 显示详细输出
-.claude/tests/run-all-tests.sh --verbose
-
-# 生成覆盖率报告
-.claude/tests/run-all-tests.sh --coverage
-```
-
-## 测试编写规范
-
-### 测试文件结构
-
-```bash
-#!/usr/bin/env bash
-# test_example.sh - Example script tests
-
-# 加载测试框架
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/../test-framework.sh"
-
-# 设置测试
-setup_test() {
-    # 创建临时测试环境
-    TEST_DIR=$(mktemp -d)
-    export TEST_ROOT="$TEST_DIR"
-}
-
-# 清理测试
-teardown_test() {
-    # 清理临时文件
-    rm -rf "$TEST_DIR"
-}
-
-# 测试函数示例
-test_function_name() {
-    describe "Function name should work correctly"
-
-    # Arrange
-    local input="test_value"
-
-    # Act
-    local result=$(function_under_test "$input")
-
-    # Assert
-    assert_equals "$result" "expected_value" "Should return expected value"
-}
-
-# 运行所有测试
-run_tests \
-    test_function_name \
-    test_another_function
-```
-
-### 断言函数
-
-- `assert_equals <actual> <expected> [message]`
-- `assert_not_equals <actual> <unexpected> [message]`
-- `assert_contains <haystack> <needle> [message]`
-- `assert_file_exists <path> [message]`
-- `assert_file_not_exists <path> [message]`
-- `assert_json_valid <json_string> [message]`
-- `assert_exit_code <expected_code> <command> [message]`
-
-### Mock 函数
-
-- `mock_git <command> <output>` - Mock Git 命令
-- `mock_file <path> <content>` - 创建 Mock 文件
-- `mock_function <function_name> <behavior>` - Mock 函数行为
-
-## 测试覆盖目标
-
-### 脚本测试覆盖率
-
-| 脚本 | 目标覆盖率 | 当前状态 | 测试文件 |
-|------|-----------|---------|---------|
-| common.sh | ≥ 80% | ⏳ 待实现 | test_common.sh |
-| check-prerequisites.sh | ≥ 80% | ⏳ 待实现 | test_check_prerequisites.sh |
-| setup-epic.sh | ≥ 80% | ⏳ 待实现 | test_setup_epic.sh |
-| mark-task-complete.sh | ≥ 80% | ⏳ 待实现 | test_mark_task_complete.sh |
-| check-task-status.sh | ≥ 80% | ⏳ 待实现 | test_check_task_status.sh |
-| validate-constitution.sh | ≥ 80% | ⏳ 待实现 | test_validate_constitution.sh |
-| generate-status-report.sh | ≥ 80% | ⏳ 待实现 | test_generate_status_report.sh |
-
-### 命令测试覆盖率
-
-| 命令 | 目标覆盖率 | 当前状态 | 测试文件 |
-|------|-----------|---------|---------|
-| /flow-init | ≥ 80% | ⏳ 待实现 | test_flow_init.sh |
-| /flow-prd | ≥ 80% | ⏳ 待实现 | test_flow_prd.sh |
-| /flow-epic | ≥ 80% | ⏳ 待实现 | test_flow_epic.sh |
-| /flow-dev | ≥ 80% | ⏳ 待实现 | test_flow_dev.sh |
-| /flow-qa | ≥ 80% | ⏳ 待实现 | test_flow_qa.sh |
-| /flow-release | ≥ 80% | ⏳ 待实现 | test_flow_release.sh |
-
-### 端到端测试
-
-| 场景 | 当前状态 | 测试文件 |
-|------|---------|---------|
-| 完整工作流 | ⏳ 待实现 | test_full_workflow.sh |
-| 中断恢复 | ⏳ 待实现 | test_interruption_recovery.sh |
-| 质量闸验证 | ⏳ 待实现 | test_quality_gates.sh |
-
-## 测试策略
-
-### 单元测试 (scripts/)
-
-**目标**: 测试每个脚本的独立功能
-
-**策略**:
-- 测试正常流程和边界情况
-- 测试错误处理和恢复
-- Mock 外部依赖 (Git, 文件系统)
-- 每个函数至少一个测试用例
-
-**示例**:
-```bash
-# 测试 get_repo_root 函数
-test_get_repo_root_in_git_repo() {
-    mock_git "rev-parse --show-toplevel" "/fake/repo"
-    result=$(get_repo_root)
-    assert_equals "$result" "/fake/repo"
-}
-
-test_get_repo_root_no_git() {
-    mock_git "rev-parse --show-toplevel" "" "exit 1"
-    result=$(get_repo_root)
-    assert_contains "$result" ".claude"
-}
-```
-
-### 集成测试 (commands/)
-
-**目标**: 测试命令的完整执行流程
-
-**策略**:
-- 测试 Entry Gate 和 Exit Gate
-- 测试命令之间的状态传递
-- 测试错误场景和恢复
-- 使用真实的脚本，Mock Git 和外部依赖
-
-**示例**:
-```bash
-test_flow_init_creates_structure() {
-    # Act
-    /flow-init "REQ-123|Test Requirement"
-
-    # Assert
-    assert_file_exists "$REQ_DIR/orchestration_status.json"
-    assert_file_exists "$REQ_DIR/EXECUTION_LOG.md"
-    assert_json_valid "$(cat $REQ_DIR/orchestration_status.json)"
-}
-```
-
-### 端到端测试 (e2e/)
-
-**目标**: 测试完整的工作流场景
-
-**策略**:
-- 模拟真实的需求开发流程
-- 测试多个命令的协作
-- 验证最终产物的正确性
-- 测试中断和恢复机制
-
-**示例**:
-```bash
-test_full_workflow_simple_requirement() {
-    # Arrange
-    setup_mock_git_repo
-
-    # Act - 执行完整流程
-    /flow-init "REQ-123|Simple Feature"
-    /flow-prd "REQ-123"
-    /flow-epic "REQ-123"
-    # ... (简化，实际测试会 mock 子代理输出)
-
-    # Assert
-    assert_file_exists "$REQ_DIR/PRD.md"
-    assert_file_exists "$REQ_DIR/EPIC.md"
-    assert_file_exists "$REQ_DIR/TASKS.md"
-}
-```
-
-## CI/CD 集成
-
-### GitHub Actions 配置
-
-```yaml
-name: Test Suite
-
-on: [push, pull_request]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - name: Run tests
-        run: .claude/tests/run-all-tests.sh
-      - name: Generate coverage report
-        run: .claude/tests/run-all-tests.sh --coverage
-      - name: Upload coverage
-        uses: codecov/codecov-action@v2
-```
-
-## 最佳实践
-
-### 1. 测试隔离
-
-- 每个测试使用独立的临时目录
-- 不依赖外部状态或全局变量
-- 清理所有临时文件
-
-### 2. Mock 外部依赖
-
-- Mock Git 命令避免修改真实仓库
-- Mock 文件系统操作避免副作用
-- Mock 网络请求避免依赖外部服务
-
-### 3. 清晰的测试命名
-
-- 使用 `test_<function>_<scenario>` 格式
-- 描述测试的意图，而不是实现
-- 使用 `describe` 添加人类可读的描述
-
-### 4. 快速反馈
-
-- 单元测试应该快速执行 (< 1秒/测试)
-- 集成测试可以稍慢 (< 5秒/测试)
-- 端到端测试可以更慢 (< 30秒/测试)
-
-### 5. 可维护性
-
-- 避免重复的测试代码
-- 使用 fixture 和 helper 函数
-- 保持测试简单和可读
-
----
-
-**最后更新**: 2025-10-01
-**状态**: ⏳ 测试框架开发中

package/.claude/tests/TODO.md

@@ -1,69 +0,0 @@
-# Testing TODO List
-
-## Active Issues
-
-### Test Environment Isolation Issues
-
-**File**: `.claude/tests/scripts/test_sync_task_marks.sh`
-
-**Status**: PARTIAL PASS (3/7 tests)
-
-**Problem**:
-- Tests 4-7 fail due to test environment isolation issues
-- The script being tested (`sync-task-marks.sh`) works correctly (verified manually)
-- Issue is with test framework's file system state management
-
-**Root Cause**:
-- Tests create directories in `$REPO_ROOT/devflow/requirements/REQ-TEST-*`
-- Subshell execution context causes directories to be inaccessible
-- Test framework's `setup_test()` and `teardown_test()` need enhancement
-
-**Current Workarounds**:
-- Using `DEVFLOW_REQ_ID` environment variable (correct approach)
-- EXIT trap for cleanup (works but doesn't fix isolation)
-
-**Tests Status**:
-- ✅ test_help_message
-- ✅ test_no_requirement_id
-- ✅ test_requirement_directory_not_found
-- ❌ test_tasks_file_not_found (directory not found in subshell)
-- ❌ test_all_tasks_completed (directory not found in subshell)
-- ❌ test_list_uncompleted_tasks (directory not found in subshell)
-- ❌ test_dry_run_shows_commands (directory not found in subshell)
-
-**Solution Needed**:
-1. Enhance test framework's environment isolation
-2. Add support for per-test working directories
-3. Improve subshell context handling for file system operations
-4. Consider using mocking strategy instead of real file system
-
-**Priority**: LOW
-- Script functionality is verified and working
-- Core error handling tests pass
-- This is a test infrastructure issue, not a code bug
-
-**Impact**: Minimal
-- Doesn't affect production code
-- Doesn't block development
-- Manual verification confirms script works correctly
-
-**Estimated Effort**: 2-4 hours
-- Need to study test framework architecture
-- Design better isolation strategy
-- Implement and verify across all test suites
-
----
-
-## Completed
-
-### Three-Layer Architecture Refactoring (2025-01-09)
-- ✅ Reorganized `.claude/rules/` to three-layer architecture
-- ✅ Reduced context usage by 55% (~100KB tokens)
-- ✅ All 7/8 test suites passing (sync-task-marks partial)
-- ✅ Documentation updated (README files)
-
-### Constitution v2.0.0 Implementation (2025-01-08)
-- ✅ 100% test coverage across all Constitution suites
-- ✅ Version consistency validation
-- ✅ Article coverage enforcement
-- ✅ Template completeness checks