cc-devflow 1.0.1

package/.claude/skills/skill-rules.json

@@ -0,0 +1,213 @@
+{
+    "version": "1.0",
+    "description": "Skill activation triggers for CC-DevFlow. Controls when skills automatically suggest or block actions.",
+    "skills": {
+        "skill-developer": {
+            "type": "domain",
+            "enforcement": "suggest",
+            "priority": "high",
+            "description": "Meta-skill for creating and managing Claude Code skills",
+            "promptTriggers": {
+                "keywords": [
+                    "skill system",
+                    "create skill",
+                    "add skill",
+                    "skill triggers",
+                    "skill rules",
+                    "hook system",
+                    "skill development",
+                    "skill-rules.json"
+                ],
+                "intentPatterns": [
+                    "(how do|how does|explain).*?skill",
+                    "(create|add|modify|build).*?skill",
+                    "skill.*?(work|trigger|activate|system)"
+                ]
+            }
+        },
+        "cc-devflow-orchestrator": {
+            "type": "domain",
+            "enforcement": "suggest",
+            "priority": "high",
+            "description": "CC-DevFlow workflow router and agent recommender. Routes users to correct commands/agents.",
+            "promptTriggers": {
+                "keywords": [
+                    "devflow",
+                    "requirement",
+                    "REQ-",
+                    "flow-init",
+                    "flow-prd",
+                    "flow-tech",
+                    "flow-ui",
+                    "flow-epic",
+                    "flow-dev",
+                    "flow-qa",
+                    "flow-release",
+                    "flow-verify",
+                    "how to write PRD",
+                    "how to design",
+                    "how to plan tasks",
+                    "create requirement",
+                    "start requirement",
+                    "workflow",
+                    "phase gate"
+                ],
+                "intentPatterns": [
+                    "(start|create|begin|init).*?(requirement|project|REQ)",
+                    "(run|execute).*?(flow|command)",
+                    "(how to|guide|explain).*?(PRD|EPIC|TASKS|design|prototype)",
+                    "what is.*?(phase gate|workflow|orchestration_status)",
+                    "(which|what).*?(command|flow|agent|next step)"
+                ]
+            },
+            "fileTriggers": {
+                "pathPatterns": [
+                    "devflow/requirements/**/*.md",
+                    "devflow/requirements/**/orchestration_status.json"
+                ]
+            }
+        },
+        "devflow-tdd-enforcer": {
+            "type": "guardrail",
+            "enforcement": "block",
+            "priority": "critical",
+            "description": "Enforces TDD order in TASKS.md - Tests MUST be marked complete before Implementation tasks",
+            "fileTriggers": {
+                "pathPatterns": [
+                    "devflow/requirements/**/TASKS.md"
+                ],
+                "contentPatterns": [
+                    "\\[x\\].*Implementation.*\\n.*\\[ \\].*Test",
+                    "\\[x\\].*\\[US\\d+\\].*Implement.*\\n.*\\[ \\].*\\[US\\d+\\].*Test"
+                ]
+            },
+            "blockMessage": "⚠️ BLOCKED - TDD Violation Detected\n\n📋 REQUIRED ACTION:\n1. Re-order TASKS.md to follow TDD sequence\n2. Mark test tasks [x] BEFORE implementation tasks\n3. Review Constitution Article VI - Test-First Development\n\nReason: CC-DevFlow enforces TDD (Tests First → Implementation)\nSource: planner agent mandate + Constitution Article VI\nFile: {file_path}\n\nCurrent Issue:\n  Implementation task marked complete\n  Test task NOT marked complete\n\n💡 SKIP: Add `@skip-tdd-check` comment or set SKIP_TDD_ENFORCER=1",
+            "skipConditions": {
+                "sessionSkillUsed": true,
+                "fileMarkers": [
+                    "@skip-tdd-check"
+                ],
+                "envOverride": "SKIP_TDD_ENFORCER"
+            }
+        },
+        "constitution-guardian": {
+            "type": "guardrail",
+            "enforcement": "block",
+            "priority": "critical",
+            "description": "Real-time Constitution compliance checker. Blocks partial implementations (Article I.1) and hardcoded secrets (Article III.1)",
+            "fileTriggers": {
+                "pathPatterns": [
+                    "devflow/requirements/**/PRD.md",
+                    "devflow/requirements/**/EPIC.md",
+                    "devflow/requirements/**/TASKS.md",
+                    "devflow/requirements/**/TECH_DESIGN.md",
+                    "devflow/requirements/**/contracts/**/*.yaml",
+                    "devflow/requirements/**/data-model.md"
+                ],
+                "contentPatterns": [
+                    "TODO.*later",
+                    "FIXME",
+                    "\\[placeholder\\]",
+                    "simplified for now",
+                    "defer to v\\d",
+                    "will complete in v\\d",
+                    "API_KEY\\s*=\\s*['\"]?[a-zA-Z0-9_-]{10,}",
+                    "SECRET\\s*=\\s*['\"]?[a-zA-Z0-9_-]+",
+                    "PASSWORD\\s*=\\s*['\"]?[^\\s]+",
+                    "TOKEN\\s*=\\s*['\"]?[a-zA-Z0-9_-]{10,}",
+                    "apiKey:\\s*['\"][^'\"]+['\"]",
+                    "password:\\s*['\"][^'\"]+['\"]",
+                    "secret:\\s*['\"][^'\"]+['\"]"
+                ]
+            },
+            "blockMessage": "⚠️ BLOCKED - Constitution Violation\n\nDetected:\n- Partial implementation (Article I.1 - NO PARTIAL IMPLEMENTATION)\n- OR Hardcoded secrets (Article III.1 - NO HARDCODED SECRETS)\n\n📋 ACTION:\n1. Complete all TODOs/FIXMEs before saving\n2. Move secrets to environment variables (.env, not committed)\n3. Review .claude/constitution/project-constitution.md v2.0.0\n4. Run /flow-verify for comprehensive check\n\nSource: Constitution Articles I.1, III.1\nFile: {file_path}\n\n💡 SKIP: Add `@constitution-verified` comment or set SKIP_CONSTITUTION_CHECK=1",
+            "skipConditions": {
+                "sessionSkillUsed": true,
+                "fileMarkers": [
+                    "@constitution-verified"
+                ],
+                "envOverride": "SKIP_CONSTITUTION_CHECK"
+            }
+        },
+        "devflow-file-standards": {
+            "type": "domain",
+            "enforcement": "suggest",
+            "priority": "medium",
+            "description": "File naming conventions, directory structure, and YAML frontmatter standards for CC-DevFlow",
+            "promptTriggers": {
+                "keywords": [
+                    "REQ-ID format",
+                    "requirement ID",
+                    "task ID",
+                    "directory structure",
+                    "file naming",
+                    "orchestration_status",
+                    "YAML frontmatter",
+                    "contract file",
+                    "where does PRD go",
+                    "file standards"
+                ],
+                "intentPatterns": [
+                    "what is.*?(format|pattern).*?(REQ|task|requirement|ID)",
+                    "where (does|should).*?(PRD|EPIC|TASKS|file|document)",
+                    "(how to|what is).*?(name|structure|organize).*?file",
+                    "what fields.*?(orchestration_status|frontmatter|YAML)"
+                ]
+            },
+            "fileTriggers": {
+                "pathPatterns": [
+                    "devflow/requirements/**/*.md",
+                    "devflow/requirements/**/orchestration_status.json",
+                    "devflow/requirements/**/contracts/**"
+                ]
+            }
+        },
+        "devflow-constitution-quick-ref": {
+            "type": "domain",
+            "enforcement": "suggest",
+            "priority": "medium",
+            "description": "Quick reference guide to CC-DevFlow Constitution v2.0.0 with links to full text",
+            "promptTriggers": {
+                "keywords": [
+                    "constitution",
+                    "constitutional",
+                    "article",
+                    "phase -1 gate",
+                    "simplicity gate",
+                    "anti-abstraction",
+                    "integration-first",
+                    "TDD mandate",
+                    "quality first",
+                    "security first",
+                    "no partial implementation",
+                    "no hardcoded secrets"
+                ],
+                "intentPatterns": [
+                    "what is.*?(constitution|article|phase -1|gate)",
+                    "(explain|show|tell me).*?(constitution|article)",
+                    "can I.*?(TODO|hardcode|BaseController|abstraction)",
+                    "should I.*?(test first|write implementation)"
+                ]
+            }
+        }
+    },
+    "notes": {
+        "enforcement_types": {
+            "suggest": "Skill suggestion appears but doesn't block execution",
+            "block": "Requires skill to be used before proceeding (guardrail)",
+            "warn": "Shows warning but allows proceeding"
+        },
+        "priority_levels": {
+            "critical": "Highest - Always trigger when matched, can block operations",
+            "high": "Important - Trigger for most matches",
+            "medium": "Moderate - Trigger for clear matches",
+            "low": "Optional - Trigger only for explicit matches"
+        },
+        "cc_devflow_customization": {
+            "pathPatterns": "All patterns match devflow/requirements/** structure",
+            "keywords": "CC-DevFlow specific terms (REQ-, flow-*, constitution, etc.)",
+            "guardra ils": "devflow-tdd-enforcer and constitution-guardian are critical guardrails",
+            "skip_conditions": "All guardrails support session skip, file markers, and env override"
+        }
+    }
+}

package/.claude/tests/README.md

@@ -0,0 +1,300 @@
+# 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

@@ -0,0 +1,69 @@
+# 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