cc-devflow 4.2.0 → 4.4.1

package/.claude/rules/rationalization-library.md

@@ -1,282 +0,0 @@
-# CC-DevFlow Rationalization Library
-
-> **Version**: 1.0.0
-> **Purpose**: Centralized defense against AI Agent rationalization attempts
-> **Source**: Extracted from superpowers TDD skill + CC-DevFlow operational experience
-
----
-
-## How to Use This Library
-
-When an agent is about to violate a Constitutional Article, they will often produce
-rationalizations. This library provides pre-crafted responses.
-
-**Pattern**:
-1. Agent produces excuse
-2. Lookup excuse in relevant Article section
-3. Respond with "Reality" column
-4. If not found, add new rationalization to library
-
----
-
-## Article I: Quality First - Rationalization Table
-
-### Iron Law
-```
-NO PARTIAL IMPLEMENTATION - COMPLETE OR NOTHING
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "This is simplified for now" | CONSTITUTIONAL VIOLATION. Complete it or don't ship it. |
-| "Will complete in v2" | Future versions don't exist. Implement fully now. |
-| "Core logic works, edge cases later" | Edge cases ARE the implementation. No later. |
-| "Time constraint" | Ship later, ship complete. Never ship incomplete. |
-| "MVP approach" | MVP = Minimum VIABLE. Viable means works completely. |
-| "Placeholder for now" | Placeholders = technical debt = future bugs. |
-| "I'll fix it before PR" | Fix it NOW. Not later. Now. |
-| "80% is good enough" | 80% = broken for 20% of users. Not good enough. |
-| "Works on my machine" | Production is not your machine. Test properly. |
-
----
-
-## Article II: Architectural Consistency - Rationalization Table
-
-### Iron Law
-```
-REUSE EXISTING CODE - NO DUPLICATION
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Faster to rewrite" | Faster now = slower forever. Find and reuse. |
-| "That code is messy" | Refactor it. Don't duplicate it. |
-| "Slightly different use case" | Extract common, parameterize difference. |
-| "I don't have time to search" | Searching takes 5 min. Maintaining duplicates takes forever. |
-| "The other code might change" | Good. Your copy will be outdated. Use shared version. |
-| "It's just a small function" | Small duplications compound. No exceptions. |
-| "I understand my version better" | Understand the shared version. That's your job. |
-
----
-
-## Article III: Security First - Rationalization Table
-
-### Iron Law
-```
-NO HARDCODED SECRETS - ENVIRONMENT VARIABLES ONLY
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "It's just for testing" | Commits are forever. Use env vars even for tests. |
-| "I'll remove it before commit" | You won't. You'll forget. Use env vars. |
-| "It's not a real secret" | Any credential is a real secret. Treat it as such. |
-| "Local development only" | Local becomes production. Start secure. |
-| "Nobody will see the repo" | Repos get shared. Git history is permanent. |
-| "I'll rotate it later" | Rotation doesn't erase history. Never commit secrets. |
-| "It's encrypted" | Encrypted secrets in code are still secrets in code. |
-
----
-
-## Article IV: Performance Accountability - Rationalization Table
-
-### Iron Law
-```
-NO RESOURCE LEAKS - ALWAYS CLEANUP
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Garbage collector will handle it" | GC doesn't close files/connections. Explicit cleanup. |
-| "Small leak, won't matter" | Small leaks become big crashes. Fix now. |
-| "It's a short-lived process" | Process lifetime is not your decision. Always cleanup. |
-| "I'll add cleanup later" | Later = never. Add cleanup with creation. |
-| "Framework handles it" | Verify that. Don't assume. |
-| "Only happens in edge case" | Edge cases run in production. Handle them. |
-
----
-
-## Article V: Maintainability - Rationalization Table
-
-### Iron Law
-```
-NO DEAD CODE - USE IT OR DELETE IT
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Might need it later" | Git history exists. Delete now, retrieve if needed. |
-| "It's just commented out" | Commented code = noise. Delete it. |
-| "Reference for future work" | Write docs. Don't keep dead code. |
-| "Someone else might need it" | They'll write their own. Delete yours. |
-| "Too risky to delete" | Tests exist. If tests pass after delete, it's safe. |
-| "I worked hard on this" | Sunk cost fallacy. Delete it. |
-
----
-
-## Article VI: Test-First Development - Rationalization Table
-
-### Iron Law
-```
-NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
-```
-
-### Rationalizations
-
-| 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. |
-| "Existing code has no tests" | You're improving it. Add tests for existing code. |
-| "Manual test faster" | Manual doesn't prove edge cases. You'll re-test every change. |
-
----
-
-## Article VII: Simplicity Gate - Rationalization Table
-
-### Iron Law
-```
-MAXIMUM 3 PROJECTS - JUSTIFY ANY ADDITIONAL COMPLEXITY
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Microservices are better" | For your scale? Monolith is simpler. Start there. |
-| "Future scalability" | YAGNI. Scale when you need to. |
-| "Separation of concerns" | Modules separate concerns. Projects add overhead. |
-| "Team autonomy" | Autonomy ≠ architectural chaos. Coordinate. |
-| "Best practices say..." | Best practices assume scale you don't have. |
-| "We might need it" | Might ≠ do. Build for now, refactor when needed. |
-
----
-
-## Article VIII: Anti-Abstraction - Rationalization Table
-
-### Iron Law
-```
-USE FRAMEWORKS DIRECTLY - NO UNNECESSARY WRAPPERS
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Abstraction for future flexibility" | YAGNI. You won't switch frameworks. |
-| "Cleaner interface" | Framework interface IS clean. Learn it. |
-| "Hide implementation details" | Framework IS implementation. Don't hide it. |
-| "Consistent with other projects" | Consistency ≠ unnecessary abstraction. |
-| "Easier testing" | Mock the framework. Don't wrap it. |
-| "Best practice pattern" | Pattern ≠ always apply. Use judgment. |
-
----
-
-## Article IX: Integration-First Testing - Rationalization Table
-
-### Iron Law
-```
-CONTRACTS FIRST - REAL ENVIRONMENTS
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Unit tests are faster" | Fast wrong tests waste time. Integration tests catch real bugs. |
-| "Mocks are simpler" | Mocks hide integration issues. Real databases find them. |
-| "CI is slow" | CI is cheap. Production bugs are expensive. |
-| "Docker is complex" | Docker is simpler than debugging integration issues. |
-| "In-memory database works" | In-memory differs from production. Test with real DB. |
-
----
-
-## Article X: Requirement Boundary - Rationalization Table
-
-### Iron Law
-```
-IMPLEMENT WHAT'S REQUESTED, NOTHING MORE
-```
-
-### Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "User might need this later" | User didn't ask. Don't add. YAGNI. |
-| "It's just a small addition" | Small additions compound. Scope creep. |
-| "This is a natural extension" | Extensions require explicit request. |
-| "Would be nice to have" | Nice ≠ required. Focus on requirements. |
-| "While I'm here anyway" | Stay on task. Create separate requirement. |
-| "It's only 5 more lines" | 5 lines = testing + docs + maintenance. Not 5 lines. |
-| "User will thank me" | User will thank you for ON-TIME, IN-SCOPE delivery. |
-| "I'm being helpful" | Helpful = following spec. Unhelpful = scope creep. |
-| "It's best practice" | Best practice: implement what's requested. |
-| "Future-proofing" | Future-proofing = over-engineering = waste. |
-| "Obvious feature" | If obvious, it should be in spec. Not in spec = don't do. |
-
----
-
-## Cross-Article Rationalizations
-
-These excuses appear across multiple Articles:
-
-| Excuse | Reality | Articles |
-|--------|---------|----------|
-| "Just this once" | No exceptions. Rules exist for this exact moment. | All |
-| "I'm being pragmatic" | Pragmatic = following rules. Shortcuts = technical debt. | All |
-| "Time is tight" | Rushed work = bugs = more time spent debugging. | All |
-| "It's obvious it works" | Nothing is obvious. Prove with tests. | I, VI |
-| "Everyone does this" | Everyone is wrong. We do it right. | All |
-| "Senior says skip it" | Constitution > authority. No skipping. | All |
-| "Emergency situation" | Emergencies especially need rules. | III, VI |
-| "This is different" | It's not different. Follow the rules. | All |
-| "Spirit over letter" | Violating letter IS violating spirit. | VI |
-| "Being practical" | Practical = disciplined. Shortcuts = impractical. | All |
-
----
-
-## Adding New Rationalizations
-
-When you encounter a new excuse not in this library:
-
-1. **Capture verbatim** - Record exact words used
-2. **Identify Article** - Which Constitutional Article does it violate?
-3. **Craft Reality response** - Brief, direct, no compromise
-4. **Add to library** - PR to update this document
-5. **Update guardrails** - Add pattern to relevant skill if blocking needed
-
----
-
-## Integration Points
-
-This library is consumed by:
-- `.claude/rules/project-constitution.md` (inline tables per Article)
-- `.claude/agents/*.md` (relevant tables per agent role)
-- `.claude/skills/devflow-tdd-enforcer/SKILL.md`
-- `.claude/skills/constitution-guardian/SKILL.md`
-- `tests/pressure-scenarios/` (test scenarios)
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/schemas/constitution.schema.json

@@ -1,43 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://cc-devflow.claude/.claude/schemas/constitution.schema.json",
-  "title": "Devflow Constitution Tracking",
-  "type": "object",
-  "required": [
-    "articles"
-  ],
-  "properties": {
-    "articles": {
-      "type": "array",
-      "minItems": 1,
-      "items": {
-        "type": "object",
-        "required": [
-          "article",
-          "status"
-        ],
-        "properties": {
-          "article": {
-            "type": "string",
-            "minLength": 1
-          },
-          "status": {
-            "type": "string",
-            "enum": [
-              "pending",
-              "in_progress",
-              "approved",
-              "waived",
-              "rejected"
-            ]
-          },
-          "notes": {
-            "type": "string"
-          }
-        },
-        "additionalProperties": false
-      }
-    }
-  },
-  "additionalProperties": true
-}

package/.claude/scripts/CLAUDE.md

@@ -1,76 +0,0 @@
-# scripts/
-> L2 | 父级: .claude/CLAUDE.md
->
-> [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
-
-## 目录定位
-
-`.claude/scripts/` 是命令层与 Skill 层共享的执行脚本库，负责状态检测、质量门禁、需求目录操作与会话恢复。
-
-## 成员清单
-
-analyze-upgrade-impact.sh: 升级影响分析脚本。
-archive-requirement.sh: 需求归档与清理脚本。
-calculate-checklist-completion.sh: Checklist 完成度统计脚本。
-calculate-quarter.sh: 时间季度计算脚本。
-check-dependencies.sh: 依赖关系检查脚本。
-check-prerequisites.sh: 流程前置条件统一校验脚本。
-check-task-status.sh: TASKS 完成状态统计脚本。
-checklist-errors.sh: Checklist 错误码与诊断脚本。
-common.sh: 脚本公共函数库（REQ 识别、日志工具等）。
-consolidate-research.sh: research 结果汇总脚本。
-create-requirement.sh: 创建需求目录与初始状态；同步 workspace 的 `.current-req`。
-delta-parser.ts: Delta 解析器。
-detect-file-conflicts.sh: 并行开发文件冲突检测脚本。
-export-contracts.sh: 合同文档导出脚本。
-extract-data-model.sh: 数据模型抽取脚本。
-flow-context-add.sh: context JSONL 条目追加脚本。
-flow-context-init.sh: context 目录初始化脚本。
-flow-context-validate.sh: context 路径验证脚本。
-flow-delta-apply.sh: Delta 应用脚本。
-flow-delta-archive.sh: Delta 归档脚本。
-flow-delta-create.sh: Delta 创建脚本。
-flow-delta-list.sh: Delta 列表脚本。
-flow-delta-status.sh: Delta 状态脚本。
-flow-quality-full.sh: 全量质量检查脚本。
-flow-quality-quick.sh: 快速质量检查脚本。
-flow-workspace-init.sh: 开发者 workspace 初始化脚本。
-flow-workspace-record.sh: workspace journal 追加记录脚本。
-generate-clarification-questions.sh: Clarify 问题生成脚本。
-generate-clarification-report.sh: Clarify 报告生成脚本。
-generate-quickstart.sh: quickstart 文档生成脚本。
-generate-research-tasks.sh: research 任务生成脚本。
-generate-status-report.sh: 状态报告聚合脚本。
-generate-tech-analysis.sh: 技术分析生成脚本。
-get-workflow-status.sh: 工作流状态读取脚本。
-locate-requirement-in-roadmap.sh: roadmap 需求定位脚本。
-manage-constitution.sh: Constitution 管理脚本。
-mark-task-complete.sh: 任务完成标记脚本。
-parse-task-dependencies.js: 任务依赖解析器。
-populate-research-tasks.sh: research 任务填充脚本。
-record-quality-error.sh: 质量错误记录脚本。
-recover-workflow.sh: 中断恢复脚本。
-run-clarify-scan.sh: Clarify 扫描执行脚本。
-run-high-review.sh: 高强度 review 执行脚本。
-run-problem-analysis.sh: 问题分析执行脚本。
-run-quality-gates.sh: 质量门禁执行脚本。
-setup-epic.sh: Epic 初始化脚本。
-setup-ralph-loop.sh: Ralph Loop 初始化脚本。
-sync-roadmap-progress.sh: roadmap 进度同步脚本。
-sync-task-marks.sh: TASKS 勾选同步脚本。
-team-dev-init.sh: Team 开发并行初始化脚本。
-team-state-recovery.sh: Team 状态恢复脚本。
-test-clarify-scan.sh: Clarify 扫描测试脚本。
-update-agent-context.sh: Agent 上下文更新脚本。
-validate-constitution.sh: Constitution 校验脚本。
-validate-hooks.sh: Hooks 校验脚本。
-validate-research.sh: research 质量校验脚本。
-validate-scope-boundary.sh: scope 边界校验脚本。
-verify-gate.sh: Gate 校验脚本。
-verify-setup.sh: 环境/安装验证脚本。
-workflow-status.ts: 工作流状态类型化读取器。
-
-## 设计约束
-
-- 需求识别统一复用 `common.sh`，避免多处正则分叉。
-- 新增脚本优先保持幂等与可重入，便于中断恢复。

package/.claude/scripts/analyze-upgrade-impact.sh

@@ -1,200 +0,0 @@
-#!/usr/bin/env bash
-# shellcheck disable=SC2312
-
-set -euo pipefail
-
-usage() {
-  cat <<'USAGE'
-Usage: scripts/bash/analyze-upgrade-impact.sh --req <requirement-dir|REQ-ID> [--compare version] [--format {text,json}]
-
-Produces PRD change detection and impact assessment reports under
-devflow/requirements/<REQ>/analysis/.
-USAGE
-}
-
-REQ=""
-COMPARE=""
-FORMAT="text"
-
-while [[ $# -gt 0 ]]; do
-  case "$1" in
-    --req)
-      shift
-      REQ="${1:-}"
-      ;;
-    --compare)
-      shift
-      COMPARE="${1:-}"
-      ;;
-    --format)
-      shift
-      FORMAT="${1:-text}"
-      ;;
-    -h|--help)
-      usage
-      exit 0
-      ;;
-    *)
-      echo "Unknown argument: $1" >&2
-      usage
-      exit 1
-      ;;
-  esac
-  shift
-done
-
-if [[ -z "$REQ" ]]; then
-  echo "Error: --req is required." >&2
-  usage
-  exit 1
-fi
-
-if [[ -d "$REQ" ]]; then
-  REQ_DIR="$(cd "$REQ" && pwd)"
-else
-  REQ_DIR="devflow/requirements/$REQ"
-fi
-
-if [[ ! -d "$REQ_DIR" ]]; then
-  echo "Error: requirement directory '$REQ_DIR' not found." >&2
-  exit 1
-fi
-
-python3 - "$REQ_DIR" "$COMPARE" "$FORMAT" <<'PY'
-from __future__ import annotations
-
-import json
-import re
-import sys
-from datetime import datetime, timezone
-from pathlib import Path
-from typing import Dict, Any
-
-req_dir = Path(sys.argv[1]).resolve()
-compare_version = sys.argv[2] or ""
-fmt = sys.argv[3]
-
-prd_current = req_dir / "PRD.md"
-if not prd_current.exists():
-    print(f"Error: {prd_current} not found.", file=sys.stderr)
-    sys.exit(1)
-
-versions_dir = req_dir / "versions"
-compare_path = None
-if compare_version:
-    compare_path = versions_dir / compare_version / "PRD.md"
-    if not compare_path.exists():
-        print(f"Warning: compare version {compare_version} not found; skipping diff.", file=sys.stderr)
-        compare_path = None
-
-current_lines = prd_current.read_text(encoding="utf-8").splitlines()
-previous_lines = compare_path.read_text(encoding="utf-8").splitlines() if compare_path else []
-
-analysis_dir = req_dir / "analysis"
-analysis_dir.mkdir(exist_ok=True, parents=True)
-timestamp = datetime.now(timezone.utc).strftime("%Y%m%d-%H%M%S")
-
-def diff_stats() -> Dict[str, Any]:
-    additions = sum(1 for line in current_lines if line.startswith("+") and "User Story" in line)
-    removals = sum(1 for line in previous_lines if line.startswith("+") and "User Story" in line)
-    breaking = 0
-    additive = 0
-    for line in current_lines:
-        if "[BREAKING]" in line or re.search(r"\bRemoved\b", line, re.IGNORECASE):
-            breaking += 1
-        if "User Story" in line or "API" in line:
-            additive += 1
-    return {
-        "userStoriesAdded": additions,
-        "userStoriesRemoved": removals,
-        "breakingMarkers": breaking,
-        "featureChanges": additive,
-    }
-
-stats = diff_stats()
-
-if stats["breakingMarkers"] > 0 or stats["userStoriesRemoved"] > 0:
-    recommendation = "MAJOR"
-elif stats["featureChanges"] > 1:
-    recommendation = "MINOR"
-else:
-    recommendation = "PATCH"
-
-change_report = analysis_dir / f"change_detection_{timestamp}.md"
-impact_report = analysis_dir / f"impact_assessment_{timestamp}.md"
-recommendation_report = analysis_dir / f"upgrade_recommendation_{timestamp}.md"
-
-change_report.write_text(
-    "\n".join(
-        [
-            f"# Change Detection — {req_dir.name}",
-            f"Generated: {datetime.now(timezone.utc).isoformat()}",
-            "",
-            f"- User stories added: {stats['userStoriesAdded']}",
-            f"- User stories removed: {stats['userStoriesRemoved']}",
-            f"- Breaking markers: {stats['breakingMarkers']}",
-            f"- Feature change mentions: {stats['featureChanges']}",
-        ]
-    )
-    + "\n",
-    encoding="utf-8",
-)
-
-impact_report.write_text(
-    "\n".join(
-        [
-            f"# Impact Assessment — {req_dir.name}",
-            "",
-            "## Code Areas Impacted",
-            "- TODO: map affected services/controllers.",
-            "",
-            "## Test Plan Impact",
-            "- TODO: identify regression suites requiring updates.",
-            "",
-            "## Deployment Considerations",
-            "- TODO: document rollout/rollback implications.",
-        ]
-    )
-    + "\n",
-    encoding="utf-8",
-)
-
-recommendation_report.write_text(
-    "\n".join(
-        [
-            f"# Upgrade Recommendation — {req_dir.name}",
-            "",
-            f"- Suggested version bump: **{recommendation}**",
-            "- Rationale:",
-            f"  * Breaking markers detected: {stats['breakingMarkers']}",
-            f"  * User stories added: {stats['userStoriesAdded']}",
-            f"  * User stories removed: {stats['userStoriesRemoved']}",
-        ]
-    )
-    + "\n",
-    encoding="utf-8",
-)
-
-summary = {
-    "requirement": req_dir.name,
-    "compareVersion": compare_version or None,
-    "recommendedBump": recommendation,
-    "statistics": stats,
-    "reports": {
-        "changeDetection": str(change_report.relative_to(req_dir)),
-        "impactAssessment": str(impact_report.relative_to(req_dir)),
-        "recommendation": str(recommendation_report.relative_to(req_dir)),
-    },
-}
-
-if fmt.lower() == "json":
-    print(json.dumps(summary, indent=2))
-else:
-    print(
-        f"Recommended bump: {recommendation}\n"
-        f"Reports:\n"
-        f"  - {summary['reports']['changeDetection']}\n"
-        f"  - {summary['reports']['impactAssessment']}\n"
-        f"  - {summary['reports']['recommendation']}"
-    )
-PY