cc-devflow 4.3.0 → 4.4.1

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

@@ -1,359 +0,0 @@
-{
-    "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/rules/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"
-            }
-        },
-        "fractal-docs-generator": {
-            "type": "domain",
-            "enforcement": "suggest",
-            "priority": "high",
-            "description": "分形文档生成器。创建目录时自动生成目录级 CLAUDE.md，实现 GEB 式递归架构文档",
-            "promptTriggers": {
-                "keywords": [
-                    "创建目录",
-                    "新建文件夹",
-                    "mkdir",
-                    "add folder",
-                    "create directory",
-                    "目录结构",
-                    "CLAUDE.md",
-                    "架构文档",
-                    "分形文档"
-                ],
-                "intentPatterns": [
-                    "(创建|新建|添加).*?(目录|文件夹|folder|directory)",
-                    "(mkdir|create|add).*?(folder|directory|dir)",
-                    "目录.*?(结构|变更|调整)",
-                    "(更新|同步).*?CLAUDE\\.md"
-                ]
-            },
-            "fileTriggers": {
-                "pathPatterns": [
-                    "**/CLAUDE.md"
-                ]
-            }
-        },
-        "file-header-guardian": {
-            "type": "domain",
-            "enforcement": "suggest",
-            "priority": "high",
-            "description": "文件头注释守护者。创建/修改代码文件时确保 @input/@output/@pos 三行契约注释存在",
-            "promptTriggers": {
-                "keywords": [
-                    "创建文件",
-                    "新建文件",
-                    "write file",
-                    "create file",
-                    "add file",
-                    "文件头注释",
-                    "头注释",
-                    "@input",
-                    "@output",
-                    "@pos"
-                ],
-                "intentPatterns": [
-                    "(创建|新建|添加|编写).*?(文件|模块|组件)",
-                    "(create|write|add).*?(file|module|component)",
-                    "(检查|更新|添加).*?(头注释|header comment)",
-                    "文件.*?(注释|documentation)"
-                ]
-            },
-            "fileTriggers": {
-                "pathPatterns": [
-                    "**/*.ts",
-                    "**/*.tsx",
-                    "**/*.js",
-                    "**/*.jsx",
-                    "**/*.py",
-                    "**/*.go",
-                    "**/*.rs",
-                    "**/*.sh"
-                ],
-                "pathExclusions": [
-                    "**/*.test.ts",
-                    "**/*.spec.ts",
-                    "**/*.d.ts",
-                    "**/node_modules/**",
-                    "**/.claude/**"
-                ]
-            }
-        },
-        "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)"
-                ]
-            }
-        },
-        "journey-coherence-checker": {
-            "type": "domain",
-            "enforcement": "suggest",
-            "priority": "high",
-            "description": "Use when completing a requirement, checking milestone progress, or asking about project status. Detects gaps between requirements, unmet dependencies, and cumulative scope drift.",
-            "promptTriggers": {
-                "keywords": [
-                    "需求完成",
-                    "REQ完成",
-                    "里程碑",
-                    "milestone",
-                    "项目进度",
-                    "可以发布",
-                    "发布前检查",
-                    "全局检查",
-                    "M1进度",
-                    "M2进度",
-                    "M3进度",
-                    "M4进度",
-                    "所有需求",
-                    "依赖满足",
-                    "journey check",
-                    "coherence check"
-                ],
-                "intentPatterns": [
-                    "(需求|REQ|requirement).*?(完成|done|finished)",
-                    "(里程碑|milestone).*?(进度|status|完成)",
-                    "(项目|project).*?(进度|status|如何)",
-                    "(可以|ready).*?(发布|release)",
-                    "(所有|all).*?(需求|requirement).*?(完成|done)",
-                    "(检查|check).*?(全局|global|依赖|dependency)"
-                ]
-            },
-            "fileTriggers": {
-                "pathPatterns": [
-                    "devflow/ROADMAP.md",
-                    "devflow/requirements/**/orchestration_status.json"
-                ]
-            }
-        },
-        "npm-release": {
-            "type": "domain",
-            "enforcement": "suggest",
-            "priority": "high",
-            "description": "Standardized release process for cc-devflow npm package. Handles version bumping, changelog updates, and publishing checks.",
-            "promptTriggers": {
-                "keywords": [
-                    "publish npm",
-                    "release version",
-                    "npm publish",
-                    "bump version",
-                    "new release",
-                    "publish package",
-                    "update changelog",
-                    "release workflow"
-                ],
-                "intentPatterns": [
-                    "(publish|release).*?(npm|package|version)",
-                    "(bump|update).*?(version|semver)",
-                    "(create|generate).*?(release|changelog)",
-                    "ready to publish",
-                    "deploy to npm"
-                ]
-            },
-            "fileTriggers": {
-                "pathPatterns": [
-                    "package.json",
-                    "CHANGELOG.md"
-                ]
-            }
-        }
-    },
-    "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/skills/tdd/SKILL.md

@@ -1,218 +0,0 @@
----
-name: flow-tdd
-description: "Enforces TDD Iron Law in flow-dev. NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST."
----
-
-# Flow TDD - Test-Driven Development Enforcement
-
-## The Iron Law
-
-```
-NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
-```
-
-This is NON-NEGOTIABLE. No exceptions. No "just this once."
-
-## The TDD Cycle
-
-```
-RED:    Write a failing test
-        → Run it
-        → Confirm it FAILS
-        → If it passes immediately → ERROR (invalid test)
-
-GREEN:  Write minimal code to pass
-        → Only enough to make the test pass
-        → No extra features
-        → No "while I'm here" additions
-
-REFACTOR: Clean up
-        → Keep tests green
-        → Improve structure
-        → Remove duplication
-```
-
-## Enforcement in flow-dev
-
-### Phase 2: Tests First
-
-```yaml
-TASKS.md Phase 2 (Tests):
-  - Write contract tests
-  - Write integration tests
-  - Write unit tests
-  - Run all tests → ALL MUST FAIL
-
-⚠️ TEST VERIFICATION CHECKPOINT:
-  → Run: npm test (or equivalent)
-  → Expected: All new tests FAIL
-  → If any test passes immediately → STOP
-  → Passing test = invalid test or code already exists
-```
-
-### Phase 3: Implementation
-
-```yaml
-TASKS.md Phase 3 (Implementation):
-  - Implement to make tests pass
-  - One test at a time
-  - Minimal code only
-
-After each implementation:
-  → Run tests
-  → Verify previously failing test now passes
-  → Verify no regressions
-```
-
-## What If Code Already Exists?
-
-If you've written code before tests:
-
-```yaml
-Option A: DELETE AND RESTART (Recommended)
-  1. Delete the implementation code
-  2. Keep only the interface/contract
-  3. Write failing tests
-  4. Re-implement with TDD
-
-Option B: WRITE TESTS THAT FAIL FIRST
-  1. Comment out the implementation
-  2. Write tests
-  3. Run tests → verify they fail
-  4. Uncomment implementation
-  5. Run tests → verify they pass
-
-NEVER: Keep code and write passing tests
-  → This is "testing after" disguised as TDD
-  → Tests that pass immediately prove nothing
-```
-
-## Rationalization Prevention
-
-| Excuse | Reality |
-|--------|---------|
-| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
-| "I'll test after" | Tests passing immediately prove nothing. |
-| "Tests after achieve same goals" | Tests-after = "what does this do?" Tests-first = "what should this do?" |
-| "Already manually tested" | Ad-hoc ≠ systematic. No record, can't re-run. |
-| "Deleting X hours is wasteful" | Sunk cost fallacy. Keeping unverified code is technical debt. |
-| "Keep as reference, write tests first" | You'll adapt it. That's testing after. Delete means delete. |
-| "Need to explore first" | Fine. Throw away exploration, start with TDD. |
-| "Test hard = design unclear" | Listen to test. Hard to test = hard to use. |
-| "TDD slows me down" | TDD faster than debugging. Pragmatic = test-first. |
-| "This is different because..." | No. This is rationalization. Follow the law. |
-| "Spirit not letter" | Violating letter IS violating spirit. No loopholes. |
-| "I'm being pragmatic, not dogmatic" | TDD IS pragmatic. Shortcuts = debugging in production = slower. |
-| "Just this once" | No exceptions. Rules exist for this exact moment. |
-
-## Red Flags - STOP
-
-If you find yourself:
-- Writing code before tests
-- Tests passing immediately
-- Saying "just this once"
-- Keeping "exploration" code
-- Writing tests that describe existing code
-
-**STOP. Delete the code. Write the test first.**
-
-## Test Quality Requirements
-
-```yaml
-Good Tests:
-  ✅ Test behavior, not implementation
-  ✅ Use realistic data
-  ✅ Cover edge cases
-  ✅ Independent (no shared state)
-  ✅ Fast (< 1 second each)
-  ✅ Descriptive names
-
-Bad Tests (Cheater Tests):
-  ❌ assert True
-  ❌ assert result is not None
-  ❌ Mock everything, test nothing
-  ❌ Test implementation details
-  ❌ Depend on execution order
-```
-
-## Error Recording Protocol
-
-当测试失败或构建错误发生时，必须立即记录到 ERROR_LOG.md:
-
-```yaml
-Error Recording Workflow:
-  1. Capture Error Context:
-     - Phase (flow-dev / T###)
-     - Error Type (Test Failure | Build Error | Runtime Error)
-     - Full error message
-     - Timestamp
-
-  2. Create ERROR_LOG.md if not exists:
-     → Use .claude/docs/templates/ERROR_LOG_TEMPLATE.md
-     → Location: devflow/requirements/${REQ_ID}/ERROR_LOG.md
-
-  3. Append Error Record:
-     ## [TIMESTAMP] E###: TITLE
-     **Phase**: flow-dev / T###
-     **Error Type**: Test Failure
-     **Error Message**:
-     ```
-     [完整错误信息]
-     ```
-     **Root Cause**: [分析后填写]
-     **Resolution**: [解决后填写]
-     **Prevention**: [可选]
-
-  4. Debug with Error Context:
-     → Read ERROR_LOG.md for similar past errors
-     → Apply attention refresh (Protocol 4)
-     → Fix the root cause, not symptoms
-
-  5. Update Record After Fix:
-     → Fill Root Cause
-     → Fill Resolution
-     → Add Prevention if applicable
-```
-
-### Error Recording Example
-
-```markdown
-## [2026-01-08T14:30:00] E001: Test Failure - User Login Validation
-
-**Phase**: flow-dev / T005
-**Error Type**: Test Failure
-**Error Message**:
-\`\`\`
-FAIL src/auth/login.test.ts
-  × should reject invalid email format
-    Expected: false
-    Received: true
-\`\`\`
-
-**Root Cause**: 正则表达式 `/^.+@.+$/` 过于宽松，接受了 `user@` 这样的无效邮箱
-**Resolution**: 更新正则为 `/^[^\s@]+@[^\s@]+\.[^\s@]+$/` 要求至少有域名和顶级域
-**Prevention**: 扩充测试用例，添加边界情况（无域名、无顶级域、特殊字符等）
-```
-
-## Integration with Constitution
-
-- **Article I**: Complete implementation includes tests
-- **Article VI**: TDD Mandate (this skill)
-- **Article IX**: Integration-first testing
-
-## Integration with Attention Refresh
-
-- **Protocol 4**: Error Recovery 时读取 ERROR_LOG.md
-- 避免重复犯相同错误
-- 从历史错误中学习
-
-## Cross-Reference
-
-- [flow-attention-refresh](../flow-attention-refresh/SKILL.md) - Protocol 4
-- [ERROR_LOG_TEMPLATE.md](../../docs/templates/ERROR_LOG_TEMPLATE.md)
-- [rationalization-library.md](../../rules/rationalization-library.md#article-vi-test-first-development---rationalization-table)
-- [project-constitution.md](../../rules/project-constitution.md#article-vi-test-first-development-测试优先开发)
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md