cc-devflow 1.0.1 → 1.0.3

package/.claude/agents/release-manager.md

@@ -17,43 +17,43 @@ Your role:
 ## Rules Integration
 You MUST follow these rules during release management:
 
-1. **Standard Patterns** (.claude/rules/core-patterns.md):
+1. **Standard Patterns**:
    - Apply Fail Fast principle: validate all quality gates before merge
    - Use Clear Errors when release criteria are not met
    - Maintain Minimal Output with focused release documentation
    - Follow Trust System principle for automated quality gate verification
 
-2. **Agent Coordination** (.claude/rules/agent-coordination.md):
+2. **Agent Coordination**:
    - Update status in LOG.md when release process begins and completes
    - Implement proper error propagation for failed quality gates
    - Coordinate with flow-orchestrator for final release approval
    - Use file locks to prevent concurrent release operations
 
-3. **Branch Operations** (.claude/guides/technical-guides/git-github-guide.md):
+3. **Branch Operations** (${DEVFLOW_CLAUDE_DIR:-.claude}/guides/technical-guides/git-github-guide.md):
    - Verify clean working directory before creating pull requests
    - Use conventional commit messages with proper Co-authored-by attribution
    - Apply squash merge strategy for clean commit history
    - Clean up feature branches after successful merge
 
-4. **GitHub Operations** (.claude/guides/technical-guides/git-github-guide.md):
+4. **GitHub Operations** (${DEVFLOW_CLAUDE_DIR:-.claude}/guides/technical-guides/git-github-guide.md):
    - Check GitHub authentication status before PR operations
    - Verify repository permissions before merge operations
    - Use structured PR descriptions with links to documentation
    - Handle permission errors and authentication failures gracefully
 
-5. **DateTime Handling** (.claude/rules/datetime.md):
+5. **DateTime Handling**:
    - Include ISO 8601 UTC timestamps in release documentation
    - Use real system time for release timestamps and changelog entries
    - Handle timezone-aware release scheduling correctly
    - Support cross-platform datetime operations in release tooling
 
-6. **DevFlow Patterns** (.claude/rules/devflow-conventions.md):
+6. **DevFlow Patterns** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/devflow-conventions.md):
    - Enforce REQ-ID format in PR titles and commit messages
    - Use standardized PR templates and release documentation
    - Apply consistent branch naming and cleanup procedures
    - Maintain complete traceability from requirements to release
 
-7. **Constitution** (.claude/constitution/project-constitution.md):
+7. **Constitution** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md):
    - Verify all Constitution checks passed before release
    - Ensure quality gates enforced (NO PARTIAL IMPLEMENTATION)
    - Validate security requirements met (NO HARDCODED SECRETS)
@@ -65,7 +65,7 @@ You MUST use the unified script infrastructure for all operations:
 1. **Get Requirement Paths**: Use `check-prerequisites.sh` to retrieve paths
    ```bash
    # Get all paths and available documents
-   .claude/scripts/check-prerequisites.sh --json --include-tasks
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --include-tasks
 
    # Expected output includes REQ_ID, REQ_DIR, and all documents
    ```
@@ -73,7 +73,7 @@ You MUST use the unified script infrastructure for all operations:
 2. **Check Task Status**: Use `check-task-status.sh` to verify completion
    ```bash
    # Get task completion status
-   .claude/scripts/check-task-status.sh --json
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-task-status.sh --json
 
    # Example output: {"total_tasks":20,"completed":20,"remaining":0,"percentage":100}
    ```
@@ -81,7 +81,7 @@ You MUST use the unified script infrastructure for all operations:
 3. **Validate Constitution**: Use `validate-constitution.sh` for final checks
    ```bash
    # Run comprehensive Constitution validation
-   .claude/scripts/validate-constitution.sh --type all --severity error --json
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/validate-constitution.sh --type all --severity error --json
 
    # Must return 0 errors before release can proceed
    ```
@@ -89,7 +89,7 @@ You MUST use the unified script infrastructure for all operations:
 4. **Log Events**: Use common.sh logging for release milestones
    ```bash
    # Log release events
-   source .claude/scripts/common.sh
+   source ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/common.sh
    log_event "$REQ_ID" "Release readiness assessment started"
    log_event "$REQ_ID" "Release plan generated - READY FOR MERGE"
    ```
@@ -115,11 +115,11 @@ When called by main agent, you will receive:
 - Expected to output: `devflow/bugs/${bugId}/RELEASE_PLAN.md`
 
 Release analysis process:
-1. **Run Prerequisites Check**: `.claude/scripts/check-prerequisites.sh --json --include-tasks`
-2. **Check Task Completion**: `.claude/scripts/check-task-status.sh --json`
+1. **Run Prerequisites Check**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --include-tasks`
+2. **Check Task Completion**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-task-status.sh --json`
    - Verify 100% task completion (remaining: 0)
    - Ensure all Phase 2 (Tests First) and Phase 3 (Implementation) tasks completed
-3. **Validate Constitution**: `.claude/scripts/validate-constitution.sh --type all --severity error --json`
+3. **Validate Constitution**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/validate-constitution.sh --type all --severity error --json`
    - Must return {"errors": 0} to proceed
    - Verify NO PARTIAL IMPLEMENTATION, NO HARDCODED SECRETS, etc.
 4. **Verify Quality Gates**: Check all quality gate documents exist and passed:

package/.claude/agents/security-reviewer.md

@@ -33,31 +33,31 @@ Called by main agent AFTER code implementation with prompt containing "security
 ## Rules Integration
 You MUST follow these rules during security review:
 
-1. **Standard Patterns** (.claude/rules/core-patterns.md):
+1. **Standard Patterns**:
    - Apply Fail Fast principle: validate security requirements before review
    - Use Clear Errors when security vulnerabilities are identified
    - Maintain Minimal Output with focused security patches and findings
    - Follow Trust System principle for established security tools and processes
 
-2. **Agent Coordination** (.claude/rules/agent-coordination.md):
+2. **Agent Coordination**:
    - Update status in LOG.md when security review begins and completes
    - Implement proper error propagation back to main agent
    - Coordinate with flow-orchestrator for security gate enforcement
    - Use file locks to prevent concurrent security analysis conflicts
 
-3. **DateTime Handling** (.claude/rules/datetime.md):
+3. **DateTime Handling**:
    - Include ISO 8601 UTC timestamps in security reports and logs
    - Use real system time for vulnerability assessment timestamps
    - Handle timezone-aware security monitoring correctly
    - Support cross-platform datetime operations in security tooling
 
-4. **DevFlow Patterns** (.claude/rules/devflow-conventions.md):
+4. **DevFlow Patterns** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/devflow-conventions.md):
    - Enforce REQ-ID format in security documentation and reports
    - Use standardized security review templates and checklists
    - Apply consistent vulnerability classification and remediation tracking
    - Maintain traceability from security findings back to implementation changes
 
-5. **Constitution** (.claude/constitution/project-constitution.md):
+5. **Constitution** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md):
    - **NO HARDCODED SECRETS**: Critical security principle - MUST detect and flag
    - **Security First**: Security is non-negotiable, blocks release if violated
    - **Input Validation**: All external inputs must be validated
@@ -69,7 +69,7 @@ You MUST use the unified script infrastructure for all operations:
 1. **Get Requirement Paths**: Use `check-prerequisites.sh` to retrieve paths
    ```bash
    # Get paths in JSON format
-   .claude/scripts/check-prerequisites.sh --json --require-epic --require-tasks
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --require-epic --require-tasks
 
    # Expected output includes REQ_ID, REQ_DIR, and all available documents
    ```
@@ -77,7 +77,7 @@ You MUST use the unified script infrastructure for all operations:
 2. **Validate Prerequisites**: Check available context before security planning
    ```bash
    # Check what documents are available
-   .claude/scripts/check-prerequisites.sh --include-tasks
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --include-tasks
 
    # Verify PRD, EPIC, and TASKS exist before creating security plan
    ```
@@ -85,7 +85,7 @@ You MUST use the unified script infrastructure for all operations:
 3. **Run Constitution Check**: Use validate-constitution.sh for automated checks
    ```bash
    # Check for hardcoded secrets and other violations
-   .claude/scripts/validate-constitution.sh --type code --severity error
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/validate-constitution.sh --type code --severity error
 
    # This provides automated baseline security validation
    ```
@@ -93,7 +93,7 @@ You MUST use the unified script infrastructure for all operations:
 4. **Log Events**: Use common.sh logging for all significant actions
    ```bash
    # Log security review events
-   source .claude/scripts/common.sh
+   source ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/common.sh
    log_event "$REQ_ID" "Security plan generation started"
    log_event "$REQ_ID" "Security analysis completed - CRITICAL findings"
    ```
@@ -127,7 +127,7 @@ When called by main agent with "security report" in prompt, you will receive:
 - **MUST OUTPUT**: `devflow/bugs/${bugId}/SECURITY_REPORT.md`
 
 ## Phase 1: Security Planning Process (Pre-Implementation)
-1. **Run Prerequisites Check**: `.claude/scripts/check-prerequisites.sh --json --require-epic --require-tasks`
+1. **Run Prerequisites Check**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --require-epic --require-tasks`
 2. **Read Documents**: Load PRD.md, EPIC.md, and TASKS.md from requirement directory
 3. **Constitution Check**: Verify PRD includes NO HARDCODED SECRETS requirement
 4. **Identify Attack Surface**: Analyze requirements for security-sensitive areas:
@@ -147,8 +147,8 @@ When called by main agent with "security report" in prompt, you will receive:
 9. **Log Event**: `log_event "$REQ_ID" "Security plan generation completed"`
 
 ## Phase 2: Security Analysis Process (Post-Implementation)
-1. **Run Prerequisites Check**: `.claude/scripts/check-prerequisites.sh --json`
-2. **Run Automated Constitution Check**: `.claude/scripts/validate-constitution.sh --type code --severity error --json`
+1. **Run Prerequisites Check**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json`
+2. **Run Automated Constitution Check**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/validate-constitution.sh --type code --severity error --json`
    - This provides baseline security validation (hardcoded secrets, etc.)
 3. **Read Implementation**: Analyze all implemented code files provided
 4. **Identify Attack Surface**: Understand actual implementation and entry points

package/.claude/agents/style-guide-generator.md

@@ -242,7 +242,7 @@ STYLE.md 是项目的**设计真理源（SSOT）**，所有 UI 相关工作必
 ### Phase 3: 文档生成与优化
 ```
 1. 使用模板生成 STYLE.md
-   → 读取 .claude/docs/templates/STYLE_TEMPLATE.md
+   → 读取 ${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/STYLE_TEMPLATE.md
    → 填充所有部分（Overview, Color Palette, Typography, ...）
    → 确保每个部分都有详细说明和示例代码
 

package/.claude/agents/tech-architect.md

@@ -36,27 +36,27 @@ Your role is to design **complete, executable technical solutions** that ensure
 ## Rules Integration
 You MUST follow these rules during technical design:
 
-1. **Standard Patterns** (.claude/rules/core-patterns.md):
+1. **Standard Patterns**:
    - Apply Fail Fast principle: validate PRD completeness before design
    - Use Clear Errors when technical requirements are ambiguous
    - Maintain Minimal Output with focused, actionable design details
    - Follow Structured Output format for consistent documentation
 
-2. **Agent Coordination** (.claude/rules/agent-coordination.md):
+2. **Agent Coordination**:
    - Update status in LOG.md when design begins and completes
    - Implement proper error handling for incomplete PRD
    - Coordinate with flow-orchestrator for requirement validation
    - Use file locks to prevent concurrent design modifications
 
-3. **DateTime Handling** (.claude/rules/datetime.md):
+3. **DateTime Handling**:
    - Include ISO 8601 UTC timestamps in YAML frontmatter
    - Use real system time for created/updated metadata
    - Handle timezone-aware deadline specifications correctly
    - Support cross-platform datetime operations
 
-4. **DevFlow Patterns** (.claude/rules/devflow-conventions.md):
+4. **DevFlow Patterns** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/devflow-conventions.md):
    - Enforce REQ-ID format validation in metadata (REQ-\\d+)
-   - Use standardized TECH_DESIGN template from .claude/docs/templates/
+   - Use standardized TECH_DESIGN template from ${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/
    - Apply consistent naming for technical components
    - Maintain traceability links to PRD and existing codebase
 
@@ -65,7 +65,7 @@ You MUST use the unified script infrastructure:
 
 1. **Get Requirement Paths**: Use `check-prerequisites.sh`
    ```bash
-   .claude/scripts/check-prerequisites.sh --json --paths-only
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --paths-only
    # Returns: {"REQ_ID":"REQ-123","REQ_DIR":"/path/to/req","PRD_FILE":"/path/to/PRD.md"}
    ```
 
@@ -78,13 +78,13 @@ You MUST use the unified script infrastructure:
 
 3. **Log Events**: Use common.sh logging
    ```bash
-   source .claude/scripts/common.sh
+   source ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/common.sh
    log_event "$REQ_ID" "Technical design started"
    log_event "$REQ_ID" "Technical design completed"
    ```
 
 ## Template Usage
-MUST use the **self-executable TECH_DESIGN_TEMPLATE.md** from `.claude/docs/templates/`:
+MUST use the **self-executable TECH_DESIGN_TEMPLATE.md** from `${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/`:
 
 1. **Load Template**: Read TECH_DESIGN_TEMPLATE.md to understand Execution Flow
 
@@ -139,7 +139,7 @@ devflow/requirements/${reqId}/
 
 ## Process
 
-1. **Run Prerequisites Check**: `.claude/scripts/check-prerequisites.sh --json --paths-only`
+1. **Run Prerequisites Check**: `${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --paths-only`
 2. **Load Tech Stack Baseline (ANTI-TECH-CREEP)**: Read CLAUDE.md to extract approved tech stack
    - **Purpose**: Prevent technology sprawl and unnecessary refactoring
    - **Baseline Source**: CLAUDE.md → "## Technical Architecture" section
@@ -163,7 +163,7 @@ devflow/requirements/${reqId}/
    - API patterns (routes/, controllers/, handlers/)
    - Security implementations (auth/, middleware/)
    - Database connections (database/, db/, config/)
-4. **Load Template**: Read `.claude/docs/templates/TECH_DESIGN_TEMPLATE.md`
+4. **Load Template**: Read `${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/TECH_DESIGN_TEMPLATE.md`
 5. **Follow Execution Flow**: Execute template's step-by-step flow
 6. **Design Architecture**:
    - System architecture diagram (text-based)

package/.claude/agents/ui-designer.md

@@ -25,26 +25,26 @@ model: inherit
 ## Rules Integration
 你MUST遵循这些规则:
 
-1. **Standard Patterns** (.claude/rules/core-patterns.md):
+1. **Standard Patterns**:
    - Apply Fail Fast: 验证PRD存在且包含UI需求
    - Use Clear Errors: 明确指出缺失的UI需求信息
    - Maintain Minimal Output: 生成单一完整的HTML文件
    - Follow Structured Output: 使用标准化的HTML5结构
 
-2. **Agent Coordination** (.claude/rules/agent-coordination.md):
+2. **Agent Coordination**:
    - Update orchestration_status.json 状态为 "ui_prototype_complete"
    - 输出到标准路径: devflow/requirements/${reqId}/UI_PROTOTYPE.html
    - Log events: "UI prototype generation started/completed"
 
-3. **DateTime Handling** (.claude/rules/datetime.md):
+3. **DateTime Handling**:
    - HTML注释中包含ISO 8601时间戳
    - 元数据中记录生成时间
 
-4. **DevFlow Patterns** (.claude/rules/devflow-conventions.md):
+4. **DevFlow Patterns** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/devflow-conventions.md):
    - 使用 UI_PROTOTYPE_TEMPLATE.md 作为生成指南
    - 在HTML注释中引用REQ-ID和PRD章节
 
-5. **Constitution** (.claude/constitution/):
+5. **Constitution** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md):
    - **Quality First**: 完整的HTML/CSS/JS实现,无部分占位符
    - **Security First**: 无硬编码API密钥,使用环境变量示例
    - **Architectural Consistency**: 遵循项目现有的设计系统(如有)
@@ -54,7 +54,7 @@ model: inherit
 
 ```bash
 # 1. 获取需求路径
-.claude/scripts/check-prerequisites.sh --json --paths-only
+${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --paths-only
 
 # 2. 加载PRD文档
 # PRD_FILE="devflow/requirements/${REQ_ID}/PRD.md"
@@ -63,13 +63,13 @@ model: inherit
 # 分析PRD中的"用户界面"/"交互设计"章节
 
 # 4. 记录事件
-source .claude/scripts/common.sh
+source ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/common.sh
 log_event "$REQ_ID" "UI prototype generation started"
 log_event "$REQ_ID" "UI prototype generation completed"
 ```
 
 ## Template Usage
-MUST使用自执行模板 `.claude/docs/templates/UI_PROTOTYPE_TEMPLATE.md`:
+MUST使用自执行模板 `${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/UI_PROTOTYPE_TEMPLATE.md`:
 
 1. **Load Template**: 读取模板理解Execution Flow
 2. **Follow Execution Flow**: 执行模板的10步生成流程:
@@ -149,7 +149,7 @@ Dieter Rams(Braun), Jony Ive(Apple), Naoto Fukasawa(无印良品), Jasper Morris
 
 1. **Run Prerequisites Check**:
    ```bash
-   .claude/scripts/check-prerequisites.sh --json --paths-only
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/check-prerequisites.sh --json --paths-only
    ```
 
 2. **Load PRD Document**:
@@ -165,7 +165,7 @@ Dieter Rams(Braun), Jony Ive(Apple), Naoto Fukasawa(无印良品), Jasper Morris
 
 4. **Load Template**:
    ```bash
-   TEMPLATE=".claude/docs/templates/UI_PROTOTYPE_TEMPLATE.md"
+   TEMPLATE="${DEVFLOW_CLAUDE_DIR:-.claude}/docs/templates/UI_PROTOTYPE_TEMPLATE.md"
    ```
 
 5. **Execute Design Phases**:
@@ -182,7 +182,7 @@ Dieter Rams(Braun), Jony Ive(Apple), Naoto Fukasawa(无印良品), Jasper Morris
 
 6. **Constitution Check**:
    ```bash
-   .claude/scripts/validate-constitution.sh --type ui --severity warning
+   ${DEVFLOW_CLAUDE_DIR:-.claude}/scripts/validate-constitution.sh --type ui --severity warning
    ```
 
 7. **Write Complete HTML**:
@@ -221,7 +221,7 @@ Dieter Rams(Braun), Jony Ive(Apple), Naoto Fukasawa(无印良品), Jasper Morris
 
 ### Constitution Compliance
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md` (v2.0.0)
 
 - [ ] **Article I - Quality First**: HTML完整无占位符,所有交互可用
 - [ ] **Article III - Security First**: 无硬编码API密钥,使用示例环境变量

package/.claude/commands/flow-constitution.md

@@ -61,7 +61,7 @@ $ARGUMENTS = "[--article I] [--verify] [--impact-report] [--amend --proposal pat
 ### 5. Apply
 ```
 → {SCRIPT:manage} apply <TYPE>
-→ 更新 .claude/constitution/project-constitution.md 版本号
+→ 更新 .claude/rules/project-constitution.md 版本号
 → 触发模板/代理/脚本同步
 → 生成 Sync Report
 ```

package/.claude/docs/SPEC_KIT_CONSTITUTION_ANALYSIS.md

@@ -150,7 +150,7 @@ consistency, simplicity, and quality.
 
 **prd-writer 示例**:
 ```markdown
-6. **Constitution** (.claude/constitution/):
+6. **Constitution** (.claude/rules/project-constitution.md):
    - **Quality First**: Ensure PRD completeness, no partial requirements
    - **Security First**: Identify and document security requirements
    - **Architecture Consistency**: Align with existing system architecture

package/.claude/docs/templates/EPIC_TEMPLATE.md

@@ -544,7 +544,7 @@ User ─(1:N)─ Post ─(1:N)─ Comment
 
 **Critical**: 这些闸门必须在架构设计之前通过，防止过度设计和复杂性蔓延
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `.claude/rules/project-constitution.md` (v2.0.0)
 
 ### Gate 1: Simplicity Gate (Article VII)
 **原则**: ≤3 Projects/Modules, No Future-Proofing
@@ -603,7 +603,7 @@ User ─(1:N)─ Post ─(1:N)─ Comment
 
 *GATE: 必须在任务生成前通过*
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `.claude/rules/project-constitution.md` (v2.0.0)
 
 ### Article I: Quality First (质量至上)
 - [ ] **I.1 - NO PARTIAL IMPLEMENTATION**: Epic 范围完整且明确？无占位符？
@@ -802,4 +802,4 @@ User ─(1:N)─ Post ─(1:N)─ Comment
 - [ ] 实施阶段清晰
 - [ ] 依赖已识别
 - [ ] 资源需求明确
-- [ ] 时间估算合理
+- [ ] 时间估算合理

package/.claude/docs/templates/PRD_TEMPLATE.md

@@ -315,7 +315,7 @@ AC1: Given {{PRECONDITION}}
 
 *GATE: 必须在 Epic 规划前通过*
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `.claude/rules/project-constitution.md` (v2.0.0)
 
 ### Article I: Quality First (质量至上)
 - [ ] **I.1 - NO PARTIAL IMPLEMENTATION**: 需求定义完整且明确？无占位符和模糊表述？

package/.claude/docs/templates/TASKS_TEMPLATE.md

@@ -459,7 +459,7 @@ With multiple developers:
 
 ### Constitution Alignment (宪法符合性)
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `.claude/rules/project-constitution.md` (v2.0.0)
 
 - [ ] **Article I - Quality First**: 没有违反 NO PARTIAL IMPLEMENTATION，所有任务完整定义
 - [ ] **Article II - Architectural Consistency**: 没有违反 NO CODE DUPLICATION，复用现有组件
@@ -495,7 +495,7 @@ With multiple developers:
 
 ### Constitution Compliance
 
-**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+**Reference**: `.claude/rules/project-constitution.md` (v2.0.0)
 
 - [ ] **Initial Check**: All 10 Articles validated at planning stage
 - [ ] **Article I-V**: Core principles checked (Quality, Architecture, Security, Performance, Maintainability)
@@ -510,7 +510,7 @@ With multiple developers:
 
 **Generated by**: planner agent
 **Based on**: PRD.md, EPIC.md
-**Constitution**: `.claude/constitution/project-constitution.md` v2.0.0
+**Constitution**: `.claude/rules/project-constitution.md` v2.0.0
 **Template Version**: 3.0.0 (Spec-Kit inspired - User Story Centric + Article-based Constitution)
 
 ---
@@ -519,5 +519,5 @@ With multiple developers:
 
 - **PRD**: `devflow/requirements/{{REQ_ID}}/PRD.md`
 - **EPIC**: `devflow/requirements/{{REQ_ID}}/EPIC.md`
-- **Constitution**: `.claude/constitution/project-constitution.md`
+- **Constitution**: `.claude/rules/project-constitution.md`
 - **Execution Log**: `devflow/requirements/{{REQ_ID}}/EXECUTION_LOG.md`

package/.claude/guides/workflow-guides/flow-orchestrator.md

@@ -30,55 +30,55 @@ type: workflow-guide
 ## Rules Integration
 You MUST follow these rules during orchestration:
 
-0. **Constitution** (.claude/constitution/):
+0. **Constitution** (${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md):
    - **Project Constitution**: Follow all constitutional principles without exception
    - **Quality Gates**: Enforce all quality gate requirements
    - **Architecture Constraints**: Adhere to architectural consistency rules
    - **Security Principles**: Apply security-first approach to all operations
 
-1. **Standard Patterns** (.claude/rules/core-patterns.md):
+1. **Standard Patterns**:
    - Apply Fail Fast principle: validate inputs immediately
    - Use Clear Errors with structured error messages
    - Maintain Minimal Output approach in user communication
    - Follow Trust System principle for sub-agent delegation
 
-2. **DevFlow Patterns** (.claude/rules/devflow-conventions.md):
+2. **DevFlow Patterns**:
    - Enforce REQ-ID format validation: REQ-\d+
    - Use standard branch naming: feature/${reqId}-${slug(title)}
    - Apply commit message format: feat(${reqId}): ${taskTitle}
    - Maintain complete document chain: PRD → EPIC → TASKS
 
-3. **Agent Coordination** (.claude/rules/agent-coordination.md):
+3. **Agent Coordination**:
    - Use file locks for concurrent access prevention
    - Update status in LOG.md after each sub-agent call
    - Implement proper error propagation between agents
    - Follow the defined sub-agent call sequence
 
-4. **Branch Operations** (.claude/guides/technical-guides/git-github-guide.md):
+4. **Branch Operations** (${DEVFLOW_CLAUDE_DIR:-.claude}/guides/technical-guides/git-github-guide.md):
    - Verify clean working directory before branch creation
    - Use conventional commit messages with Co-authored-by
    - Enforce quality gates before any push operations
    - Clean up branches after successful merge
 
-5. **GitHub Operations** (.claude/guides/technical-guides/git-github-guide.md):
+5. **GitHub Operations** (${DEVFLOW_CLAUDE_DIR:-.claude}/guides/technical-guides/git-github-guide.md):
    - Check authentication status before PR operations
    - Verify repository is not a template before modifications
    - Use structured PR descriptions with links to documentation
    - Handle permission errors gracefully
 
-6. **Test Execution** (.claude/rules/test-execution.md):
+6. **Test Execution**:
    - Delegate all testing to qa-tester sub-agent
    - Capture verbose test output for audit trail
    - Enforce minimum coverage thresholds
    - Never mock external services in tests
 
-7. **DateTime Handling** (.claude/rules/datetime.md):
+7. **DateTime Handling**:
    - Use real system time in ISO 8601 UTC format
    - Include timestamps in all YAML frontmatter
    - Handle timezone-aware operations correctly
    - Support cross-platform datetime operations
 
-8. **MCP Integration** (.claude/rules/mcp-integration.md):
+8. **MCP Integration**:
    - Use WebFetch tool for all external content retrieval
    - Apply URL validation rules for security
    - Implement retry logic with exponential backoff
@@ -86,7 +86,7 @@ You MUST follow these rules during orchestration:
 
 Steps:
 0) Constitutional Validation
-   - Read and internalize .claude/constitution/ requirements
+   - Read and internalize ${DEVFLOW_CLAUDE_DIR:-.claude}/rules/project-constitution.md requirements
    - Validate all inputs against constitutional principles
    - Ensure current environment meets constitutional standards
    - Apply constitutional constraints to the entire workflow

package/.claude/scripts/check-task-status.sh

@@ -28,6 +28,30 @@ TASK_ID=""
 JSON_MODE=false
 VERBOSE=false
 
+count_matches() {
+    local pattern="$1"
+    local file="$2"
+    local count
+    count=$(grep -c "$pattern" "$file" 2>/dev/null || true)
+    count=${count//[[:space:]]/}
+    printf '%s' "${count:-0}"
+}
+
+count_phase_tasks() {
+    local header="$1"
+    local mode="$2"
+    local file="$3"
+    awk -v header="$header" -v mode="$mode" '
+        $0 ~ header {in_section=1; next}
+        in_section && /^## / {exit}
+        in_section {
+            if (mode == "all" && $0 ~ /^- \[/) {count++}
+            if (mode == "complete" && $0 ~ /^- \[x\]/) {count++}
+        }
+        END {print count+0}
+    ' "$file"
+}
+
 while [[ $# -gt 0 ]]; do
     case "$1" in
         --json)
@@ -132,8 +156,8 @@ if [[ ! -f "$TASKS_FILE" ]]; then
 fi
 
 # Count tasks
-TOTAL_INCOMPLETE=$(grep -c "^\- \[ \]" "$TASKS_FILE" 2>/dev/null || echo "0")
-TOTAL_COMPLETE=$(grep -c "^\- \[x\]" "$TASKS_FILE" 2>/dev/null || echo "0")
+TOTAL_INCOMPLETE=$(count_matches "^\- \[ \]" "$TASKS_FILE")
+TOTAL_COMPLETE=$(count_matches "^\- \[x\]" "$TASKS_FILE")
 TOTAL_TASKS=$((TOTAL_INCOMPLETE + TOTAL_COMPLETE))
 
 # Calculate percentage
@@ -189,24 +213,24 @@ fi
 
 # Get phase breakdown - ensure all values are clean integers
 if grep -q "^## Phase 1:" "$TASKS_FILE" 2>/dev/null; then
-    PHASE_1_TOTAL=$(grep "^## Phase 1:" -A 100 "$TASKS_FILE" | grep -c "^\- \[")
-    PHASE_1_COMPLETE=$(grep "^## Phase 1:" -A 100 "$TASKS_FILE" | grep "^\- \[x\]" | wc -l | tr -d ' \n')
+    PHASE_1_TOTAL=$(count_phase_tasks "^## Phase 1:" "all" "$TASKS_FILE")
+    PHASE_1_COMPLETE=$(count_phase_tasks "^## Phase 1:" "complete" "$TASKS_FILE")
 else
     PHASE_1_TOTAL=0
     PHASE_1_COMPLETE=0
 fi
 
 if grep -q "^## Phase 2:" "$TASKS_FILE" 2>/dev/null; then
-    PHASE_2_TOTAL=$(grep "^## Phase 2:" -A 100 "$TASKS_FILE" | grep -c "^\- \[")
-    PHASE_2_COMPLETE=$(grep "^## Phase 2:" -A 100 "$TASKS_FILE" | grep "^\- \[x\]" | wc -l | tr -d ' \n')
+    PHASE_2_TOTAL=$(count_phase_tasks "^## Phase 2:" "all" "$TASKS_FILE")
+    PHASE_2_COMPLETE=$(count_phase_tasks "^## Phase 2:" "complete" "$TASKS_FILE")
 else
     PHASE_2_TOTAL=0
     PHASE_2_COMPLETE=0
 fi
 
 if grep -q "^## Phase 3:" "$TASKS_FILE" 2>/dev/null; then
-    PHASE_3_TOTAL=$(grep "^## Phase 3:" -A 100 "$TASKS_FILE" | grep -c "^\- \[")
-    PHASE_3_COMPLETE=$(grep "^## Phase 3:" -A 100 "$TASKS_FILE" | grep "^\- \[x\]" | wc -l | tr -d ' \n')
+    PHASE_3_TOTAL=$(count_phase_tasks "^## Phase 3:" "all" "$TASKS_FILE")
+    PHASE_3_COMPLETE=$(count_phase_tasks "^## Phase 3:" "complete" "$TASKS_FILE")
 else
     PHASE_3_TOTAL=0
     PHASE_3_COMPLETE=0
@@ -261,4 +285,4 @@ else
         echo "────────────────────────────────────────"
         grep "^\- \[" "$TASKS_FILE"
     fi
-fi
+fi

package/.claude/scripts/manage-constitution.sh

@@ -26,8 +26,8 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
 source "$SCRIPT_DIR/common.sh"
-CONSTITUTION_FILE="$REPO_ROOT/.claude/constitution/project-constitution.md"
-AMENDMENT_DIR="$REPO_ROOT/.claude/constitution/amendments"
+CONSTITUTION_FILE="$REPO_ROOT/.claude/rules/project-constitution.md"
+AMENDMENT_DIR="$REPO_ROOT/.claude/rules/amendments"
 
 # 需要更新版本号的文件模式
 declare -a FILES_TO_UPDATE=(

package/.claude/scripts/validate-constitution.sh

@@ -6,7 +6,7 @@
 # Validates all 10 Constitutional Articles (Article I-X).
 # Inspired by spec-kit's quality gate philosophy.
 #
-# Constitution Reference: .claude/constitution/project-constitution.md
+# Constitution Reference: .claude/rules/project-constitution.md
 # Article I: Quality First
 # Article II: Architectural Consistency
 # Article III: Security First

package/.claude/skills/cc-devflow-orchestrator/SKILL.md

@@ -181,7 +181,7 @@ status: "released"
 ### Constitution violation?
 - **Real-time check**: constitution-guardian guardrail (PreToolUse hook)
 - **Batch validation**: Run `.claude/scripts/validate-constitution.sh`
-- **Reference**: See [.claude/constitution/project-constitution.md](.claude/constitution/project-constitution.md) v2.0.0
+- **Reference**: See `.claude/rules/project-constitution.md` v2.0.0
 
 ### TDD order violated?
 - **Real-time check**: devflow-tdd-enforcer guardrail (PreToolUse hook)