feat: add category and scope to specs for enhanced filtering and organization

- Introduced SpecCategory and SpecScope types to categorize specs by workflow stage and scope (global/project).
- Updated Spec interface to include category and scope properties.
- Enhanced SpecCard component to display category and scope badges.
- Implemented category and scope filtering in SpecsSettingsPage.
- Updated localization files to support new category and scope labels.
- Modified spec loading commands to utilize category instead of keywords.
- Adjusted spec index builder to handle category and scope during spec parsing.
- Updated seed documents to include category information.

.ccw/workflows/cli-templates/prompts/rules-tech-rules-agent-prompt.txt

@@ -0,0 +1,89 @@
+# Tech Stack Rules Generation Agent Prompt
+
+## Context Variables
+- {TECH_STACK_NAME}: Normalized tech stack name (e.g., "typescript-react")
+- {PRIMARY_LANG}: Primary language (e.g., "typescript")
+- {FILE_EXT}: File extension pattern (e.g., "{ts,tsx}")
+- {FRAMEWORK_TYPE}: frontend | backend | fullstack | library
+- {COMPONENTS}: Array of tech components
+- {OUTPUT_DIR}: .claude/rules/tech/{TECH_STACK_NAME}/
+
+## Agent Instructions
+
+Generate path-conditional rules for Claude Code automatic loading.
+
+### Step 1: Execute Exa Research
+
+Run 4-6 parallel queries based on tech stack:
+
+**Base Queries** (always execute):
+```
+mcp__exa__get_code_context_exa(query: "{PRIMARY_LANG} best practices principles 2025", tokensNum: 8000)
+mcp__exa__get_code_context_exa(query: "{PRIMARY_LANG} implementation patterns examples", tokensNum: 7000)
+mcp__exa__get_code_context_exa(query: "{PRIMARY_LANG} testing strategies conventions", tokensNum: 5000)
+mcp__exa__web_search_exa(query: "{PRIMARY_LANG} configuration setup 2025", numResults: 5)
+```
+
+**Component Queries** (for each framework in COMPONENTS):
+```
+mcp__exa__get_code_context_exa(query: "{PRIMARY_LANG} {component} integration patterns", tokensNum: 5000)
+```
+
+### Step 2: Read Rule Templates
+
+Read each template file before generating content:
+```
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-core.txt)
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-patterns.txt)
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-testing.txt)
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-config.txt)
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-api.txt)       # Only if backend/fullstack
+Read(~/.ccw/workflows/cli-templates/prompts/rules/rule-components.txt) # Only if frontend/fullstack
+```
+
+### Step 3: Generate Rule Files
+
+Create directory and write files:
+```bash
+mkdir -p "{OUTPUT_DIR}"
+```
+
+**Always Generate**:
+- core.md (from rule-core.txt template)
+- patterns.md (from rule-patterns.txt template)
+- testing.md (from rule-testing.txt template)
+- config.md (from rule-config.txt template)
+
+**Conditional**:
+- api.md: Only if FRAMEWORK_TYPE == 'backend' or 'fullstack'
+- components.md: Only if FRAMEWORK_TYPE == 'frontend' or 'fullstack'
+
+### Step 4: Write Metadata
+
+```json
+{
+  "tech_stack": "{TECH_STACK_NAME}",
+  "primary_lang": "{PRIMARY_LANG}",
+  "file_ext": "{FILE_EXT}",
+  "framework_type": "{FRAMEWORK_TYPE}",
+  "components": ["{COMPONENTS}"],
+  "generated_at": "{ISO_TIMESTAMP}",
+  "source": "exa-research",
+  "files_generated": ["core.md", "patterns.md", "testing.md", "config.md", ...]
+}
+```
+
+### Step 5: Report Completion
+
+Provide summary:
+- Files created with their path patterns
+- Exa queries executed (count)
+- Sources consulted (count)
+
+## Critical Requirements
+
+1. Every .md file MUST start with `paths` YAML frontmatter
+2. Use {FILE_EXT} consistently across all rule files
+3. Synthesize Exa research into actionable rules
+4. Include code examples from Exa sources
+5. Keep each file focused on its specific domain

.ccw/workflows/cli-templates/prompts/test-suggestions-enhancement.txt

@@ -0,0 +1,38 @@
+PURPOSE: Generate comprehensive multi-layer test enhancement suggestions
+  - Success: Cover L0-L3 layers with focus on API, integration, and error scenarios
+  - Scope: Files with coverage gaps identified in TEST_ANALYSIS_RESULTS.md
+  - Goal: Provide specific, actionable test case suggestions that increase coverage completeness
+
+TASK:
+  • L1 (Unit Tests): Suggest edge cases, boundary conditions, error paths, state transitions
+  • L2.1 (Integration): Suggest module interaction patterns, dependency injection scenarios
+  • L2.2 (API Contracts): Suggest request/response test cases, validation, status codes, error responses
+  • L2.4 (External APIs): Suggest mock strategies, failure scenarios, timeout handling, retry logic
+  • L2.5 (Failure Modes): Suggest exception hierarchies, error propagation, recovery strategies
+  • Cross-cutting: Suggest performance test cases, security considerations
+
+MODE: analysis
+
+CONTEXT: @.workflow/active/{test-session-id}/.process/TEST_ANALYSIS_RESULTS.md
+  Memory: Project type, test framework, existing test patterns, coverage gaps
+
+EXPECTED: Markdown report with structured test enhancement suggestions organized by:
+  1. File-level test requirements (per file needing tests)
+  2. Layer-specific test cases (L1, L2.1, L2.2, L2.4, L2.5)
+  3. Each suggestion includes:
+     - Test type and layer (e.g., "L2.2 API Contract Test")
+     - Specific test case description (e.g., "POST /api/users - Invalid email format")
+     - Expected behavior (e.g., "Returns 400 with validation error message")
+     - Dependencies/mocks needed (e.g., "Mock email service")
+     - Success criteria (e.g., "Status 400, error.field === 'email'")
+  4. Test ordering/dependencies (which tests should run first)
+  5. Integration test strategies (how components interact)
+  6. Error scenario matrix (all failure modes covered)
+
+CONSTRAINTS:
+  - Focus on identified coverage gaps from TEST_ANALYSIS_RESULTS.md
+  - Prioritize API tests, integration tests, and error scenarios
+  - No code generation - suggestions only with sufficient detail for implementation
+  - Consider project conventions and existing test patterns
+  - Each suggestion should be actionable and specific (not generic)
+  - Output format: Markdown with clear section headers

.ccw/workflows/cli-templates/prompts/workflow-codex-feasibility-validation.txt

@@ -0,0 +1,176 @@
+Validate technical feasibility and identify implementation risks for proposed solution design.
+
+## CORE CHECKLIST ⚡
+□ Read context-package.json and gemini-solution-design.md
+□ Assess complexity, validate technology choices
+□ Evaluate performance and security implications
+□ Focus on TECHNICAL FEASIBILITY and RISK ASSESSMENT
+□ Write output to specified .workflow/active/{session_id}/.process/ path
+
+## PREREQUISITE ANALYSIS
+
+### Required Input Files
+1. **context-package.json**: Task requirements, source files, tech stack
+2. **gemini-solution-design.md**: Proposed solution design and architecture
+3. **workflow-session.json**: Session state and context
+4. **CLAUDE.md**: Project standards and conventions
+
+### Analysis Dependencies
+- Review Gemini's proposed solution design
+- Validate against actual codebase capabilities
+- Assess implementation complexity realistically
+- Identify gaps between design and execution
+
+## REQUIRED VALIDATION
+
+### 1. Feasibility Assessment
+- **Complexity Rating**: Rate technical complexity (1-5 scale)
+  - 1: Trivial - straightforward implementation
+  - 2: Simple - well-known patterns
+  - 3: Moderate - some challenges
+  - 4: Complex - significant challenges
+  - 5: Very Complex - high risk, major unknowns
+
+- **Resource Requirements**: Estimate development effort
+  - Development time (hours/days/weeks)
+  - Required expertise level
+  - Infrastructure needs
+
+- **Technology Compatibility**: Validate proposed tech stack
+  - Framework version compatibility
+  - Library maturity and support
+  - Integration with existing systems
+
+### 2. Risk Analysis
+- **Implementation Risks**: Technical challenges and blockers
+  - Unknown implementation patterns
+  - Missing capabilities or APIs
+  - Breaking changes to existing code
+
+- **Integration Challenges**: System integration concerns
+  - Data format compatibility
+  - API contract changes
+  - Dependency conflicts
+
+- **Performance Concerns**: Performance and scalability risks
+  - Resource consumption (CPU, memory, I/O)
+  - Latency and throughput impact
+  - Caching and optimization needs
+
+- **Security Concerns**: Security vulnerabilities and threats
+  - Authentication/authorization gaps
+  - Data exposure risks
+  - Compliance violations
+
+### 3. Implementation Validation
+- **Development Approach**: Validate proposed implementation strategy
+  - Verify module dependency order
+  - Assess incremental development feasibility
+  - Evaluate testing approach
+
+- **Quality Standards**: Validate quality requirements
+  - Test coverage achievability
+  - Performance benchmark realism
+  - Documentation completeness
+
+- **Maintenance Implications**: Long-term sustainability
+  - Code maintainability assessment
+  - Technical debt evaluation
+  - Evolution and extensibility
+
+### 4. Code Target Verification
+Review Gemini's proposed code targets:
+- **Validate existing targets**: Confirm file:function:lines exist
+- **Assess new file targets**: Evaluate necessity and placement
+- **Identify missing targets**: Suggest additional modification points
+- **Refine target specifications**: Provide more precise line numbers if possible
+
+### 5. Recommendations
+- **Must-Have Requirements**: Critical requirements for success
+- **Optimization Opportunities**: Performance and quality improvements
+- **Security Controls**: Essential security measures
+- **Risk Mitigation**: Strategies to reduce identified risks
+
+## OUTPUT REQUIREMENTS
+
+### Output File
+**Path**: `.workflow/active/{session_id}/.process/codex-feasibility-validation.md`
+**Format**: Follow structure from `~/.ccw/workflows/cli-templates/prompts/workflow/analysis-results-structure.txt`
+
+### Required Sections
+Focus on these sections from the template:
+- Executive Summary (with Codex perspective)
+- Current State Analysis (validation findings)
+- Implementation Strategy (feasibility assessment)
+- Solution Optimization (risk mitigation)
+- Confidence Scores (technical feasibility focus)
+
+### Content Guidelines
+- ✅ Focus on technical feasibility and risk assessment
+- ✅ Verify code targets from Gemini's design
+- ✅ Provide concrete risk mitigation strategies
+- ✅ Quantify complexity and effort estimates
+- ❌ Do NOT create task breakdowns
+- ❌ Do NOT provide step-by-step implementation guides
+- ❌ Do NOT include code examples
+
+## VALIDATION METHODOLOGY
+
+### Complexity Scoring
+Rate each aspect on 1-5 scale:
+- Technical Complexity
+- Integration Complexity
+- Performance Risk
+- Security Risk
+- Maintenance Burden
+
+### Risk Classification
+- **LOW**: Minor issues, easily addressable
+- **MEDIUM**: Manageable challenges with clear mitigation
+- **HIGH**: Significant concerns requiring major mitigation
+- **CRITICAL**: Fundamental viability threats
+
+### Feasibility Judgment
+- **PROCEED**: Technically feasible with acceptable risk
+- **PROCEED_WITH_MODIFICATIONS**: Feasible but needs adjustments
+- **RECONSIDER**: High risk, major changes needed
+- **REJECT**: Not feasible with current approach
+
+## CONTEXT INTEGRATION
+
+### Gemini Analysis Integration
+- Review proposed architecture and design decisions
+- Validate assumptions and technology choices
+- Cross-check code targets against actual codebase
+- Assess realism of performance targets
+
+### Codebase Reality Check
+- Verify existing code capabilities
+- Identify actual technical constraints
+- Assess team skill compatibility
+- Evaluate infrastructure readiness
+
+### Session Context
+- Consider session history and previous decisions
+- Align with project architecture standards
+- Respect existing patterns and conventions
+
+## EXECUTION MODE
+
+**Mode**: Analysis with write permission for output file
+**CLI Tool**: Codex with --skip-git-repo-check -s danger-full-access
+**Timeout**: 60-90 minutes for complex tasks
+**Output**: Single file codex-feasibility-validation.md
+**Trigger**: Only for complex tasks (>6 modules)
+
+## VERIFICATION CHECKLIST ✓
+□ context-package.json and gemini-solution-design.md read
+□ Complexity rated on 1-5 scale with justification
+□ All risk categories assessed (technical, integration, performance, security)
+□ Code targets verified and refined
+□ Risk mitigation strategies provided
+□ Resource requirements estimated
+□ Final feasibility judgment (PROCEED/RECONSIDER/REJECT)
+□ Output written to .workflow/active/{session_id}/.process/codex-feasibility-validation.md
+
+Focus: Technical feasibility validation with realistic risk assessment and mitigation strategies.

.ccw/workflows/cli-templates/prompts/workflow-gemini-solution-design.txt

@@ -0,0 +1,131 @@
+Analyze and design optimal solution with comprehensive architecture evaluation and design decisions.
+
+## CORE CHECKLIST ⚡
+□ Read context-package.json to understand task requirements, source files, tech stack
+□ Analyze current architecture patterns and code structure
+□ Propose solution design with key decisions and rationale
+□ Focus on SOLUTION IMPROVEMENTS and KEY DESIGN DECISIONS
+□ Write output to specified .workflow/active/{session_id}/.process/ path
+
+## ANALYSIS PRIORITY
+
+### Source Hierarchy
+1. **PRIMARY**: Individual role analysis.md files (system-architect, ui-designer, data-architect, etc.)
+   - Technical details and implementation considerations
+   - Architecture Decision Records (ADRs)
+   - Design decision context and rationale
+
+2. **SECONDARY**: role analysis documents
+   - Integrated requirements across roles
+   - Cross-role alignment and dependencies
+   - Unified feature specifications
+
+3. **REFERENCE**: guidance-specification.md
+   - Discussion context and background
+   - Initial problem framing
+
+## REQUIRED ANALYSIS
+
+### 1. Current State Assessment
+- Identify existing architectural patterns and code structure
+- Map integration points and dependencies
+- Evaluate technical debt and pain points
+- Assess framework compatibility and constraints
+
+### 2. Solution Design
+- Propose core architecture principles and approach
+- Design component architecture and data flow
+- Specify API contracts and integration strategy
+- Define technology stack with justification
+
+### 3. Key Design Decisions
+For each critical decision:
+- **Decision**: What is being decided
+- **Rationale**: Why this approach
+- **Alternatives Considered**: Other options and their tradeoffs
+- **Impact**: Implications on architecture, performance, maintainability
+
+Minimum 2 key decisions required.
+
+### 4. Code Modification Targets
+Identify specific code locations for changes:
+- **Existing files**: `file:function:lines` format (e.g., `src/auth/login.ts:validateUser:45-52`)
+- **New files**: `file` only (e.g., `src/auth/PasswordReset.ts`)
+- **Unknown lines**: `file:function:*` (e.g., `src/auth/service.ts:refreshToken:*`)
+
+For each target:
+- Type: Modify existing | Create new
+- Modification/Purpose: What changes needed
+- Rationale: Why this target
+
+### 5. Critical Insights
+- Strengths: What works well in current/proposed design
+- Gaps: Missing capabilities or concerns
+- Risks: Technical, integration, performance, security
+- Optimization Opportunities: Performance, security, code quality
+
+### 6. Feasibility Assessment
+- Technical Complexity: Rating and analysis
+- Performance Impact: Expected characteristics
+- Resource Requirements: Development effort
+- Maintenance Burden: Ongoing considerations
+
+## OUTPUT REQUIREMENTS
+
+### Output File
+**Path**: `.workflow/active/{session_id}/.process/gemini-solution-design.md`
+**Format**: Follow structure from `~/.ccw/workflows/cli-templates/prompts/workflow/analysis-results-structure.txt`
+
+### Required Sections
+- Executive Summary with feasibility score
+- Current State Analysis
+- Proposed Solution Design with 2+ key decisions
+- Implementation Strategy with code targets
+- Solution Optimization (performance, security, quality)
+- Critical Success Factors
+- Confidence Scores with recommendation
+
+### Content Guidelines
+- ✅ Focus on solution improvements and key design decisions
+- ✅ Include rationale, alternatives, and tradeoffs for decisions
+- ✅ Provide specific code targets in correct format
+- ✅ Quantify assessments with scores (X/5)
+- ❌ Do NOT create task lists or implementation steps
+- ❌ Do NOT include code examples or snippets
+- ❌ Do NOT create project management timelines
+
+## CONTEXT INTEGRATION
+
+### Session Context
+- Load context-package.json for task requirements
+- Reference workflow-session.json for session state
+- Review CLAUDE.md for project standards
+
+### Brainstorm Context
+If brainstorming artifacts exist:
+- Prioritize individual role analysis.md files
+- Use role analysis documents for integrated view
+- Reference guidance-specification.md for context
+
+### Codebase Context
+- Identify similar patterns in existing code
+- Evaluate success/failure of current approaches
+- Ensure consistency with project architecture
+
+## EXECUTION MODE
+
+**Mode**: Analysis with write permission for output file
+**CLI Tool**: Gemini wrapper with --approval-mode yolo
+**Timeout**: 40-60 minutes based on complexity
+**Output**: Single file gemini-solution-design.md
+
+## VERIFICATION CHECKLIST ✓
+□ context-package.json read and analyzed
+□ All 7 required sections present in output
+□ 2+ key design decisions with rationale and alternatives
+□ Code targets specified in correct format
+□ Feasibility scores provided (X/5)
+□ Final recommendation (PROCEED/RECONSIDER/REJECT)
+□ Output written to .workflow/active/{session_id}/.process/gemini-solution-design.md
+
+Focus: Comprehensive solution design emphasizing architecture decisions and critical insights.

.ccw/workflows/cli-templates/prompts/workflow-impl-plan-template.txt

@@ -0,0 +1,286 @@
+IMPL_PLAN.md Template - Implementation Plan Document Structure
+
+## Document Frontmatter
+
+```yaml
+---
+identifier: WFS-{session-id}
+source: "User requirements" | "File: path" | "Issue: ISS-001"
+analysis: .workflow/active//{session-id}/.process/ANALYSIS_RESULTS.md
+artifacts: .workflow/active//{session-id}/.brainstorming/
+context_package: .workflow/active//{session-id}/.process/context-package.json  # CCW smart context
+workflow_type: "standard | tdd | design"  # Indicates execution model
+verification_history:  # CCW quality gates
+  concept_verify: "passed | skipped | pending"
+  action_plan_verify: "pending"
+phase_progression: "brainstorm → context → analysis → concept_verify → planning"  # CCW workflow phases
+---
+```
+
+## Document Structure
+
+# Implementation Plan: {Project Title}
+
+## 1. Summary
+Core requirements, objectives, technical approach summary (2-3 paragraphs max).
+
+**Core Objectives**:
+- [Key objective 1]
+- [Key objective 2]
+
+**Technical Approach**:
+- [High-level approach]
+
+## 2. Context Analysis
+
+### CCW Workflow Context
+**Phase Progression**:
+- ✅ Phase 1: Brainstorming (role analyses generated)
+- ✅ Phase 2: Context Gathering (context-package.json: {N} files, {M} modules analyzed)
+- ✅ Phase 3: Enhanced Analysis (ANALYSIS_RESULTS.md: Gemini/Qwen/Codex parallel insights)
+- ✅ Phase 4: Concept Verification ({X} clarifications answered, role analyses updated | skipped)
+- ⏳ Phase 5: Action Planning (current phase - generating IMPL_PLAN.md)
+
+**Quality Gates**:
+- concept-verify: ✅ Passed (0 ambiguities remaining) | ⏭️ Skipped (user decision) | ⏳ Pending
+- plan-verify: ⏳ Pending (recommended before /workflow:execute)
+
+**Context Package Summary**:
+- **Focus Paths**: {list key directories from context-package.json}
+- **Key Files**: {list primary files for modification}
+- **Module Depth Analysis**: {from get_modules_by_depth.sh output}
+- **Smart Context**: {total file count} files, {module count} modules, {dependency count} dependencies identified
+
+### Project Profile
+- **Type**: Greenfield/Enhancement/Refactor
+- **Scale**: User count, data volume, complexity
+- **Tech Stack**: Primary technologies
+- **Timeline**: Duration and milestones
+
+### Module Structure
+```
+[Directory tree showing key modules]
+```
+
+### Dependencies
+**Primary**: [Core libraries and frameworks]
+**APIs**: [External services]
+**Development**: [Testing, linting, CI/CD tools]
+
+### Patterns & Conventions
+- **Architecture**: [Key patterns like DI, Event-Driven]
+- **Component Design**: [Design patterns]
+- **State Management**: [State strategy]
+- **Code Style**: [Naming, TypeScript coverage]
+
+## 3. Brainstorming Artifacts Reference
+
+### Artifact Usage Strategy
+**Primary Reference (role analyses)**:
+- **What**: Role-specific analyses from brainstorming providing multi-perspective insights
+- **When**: Every task references relevant role analyses for requirements and design decisions
+- **How**: Extract requirements, architecture decisions, UI/UX patterns from applicable role documents
+- **Priority**: Collective authoritative source - multiple role perspectives provide comprehensive coverage
+- **CCW Value**: Maintains role-specific expertise while enabling cross-role integration during planning
+
+**Context Intelligence (context-package.json)**:
+- **What**: Smart context gathered by CCW's context-gather phase
+- **Content**: Focus paths, dependency graph, existing patterns, module structure
+- **Usage**: Tasks load this via `flow_control.preparatory_steps` for environment setup
+- **CCW Value**: Automated intelligent context discovery replacing manual file exploration
+
+**Technical Analysis (ANALYSIS_RESULTS.md)**:
+- **What**: Gemini/Qwen/Codex parallel analysis results
+- **Content**: Optimization strategies, risk assessment, architecture review, implementation patterns
+- **Usage**: Referenced in task planning for technical guidance and risk mitigation
+- **CCW Value**: Multi-model parallel analysis providing comprehensive technical intelligence
+
+### Integrated Specifications (Highest Priority)
+- **role analyses**: Comprehensive implementation blueprint
+  - Contains: Architecture design, UI/UX guidelines, functional/non-functional requirements, implementation roadmap, risk assessment
+
+### Supporting Artifacts (Reference)
+- **guidance-specification.md**: Role-specific discussion points and analysis framework
+- **system-architect/analysis.md**: Detailed architecture specifications
+- **ui-designer/analysis.md**: Layout and component specifications
+- **product-manager/analysis.md**: Product vision and user stories
+
+**Artifact Priority in Development**:
+1. role analyses (primary reference for all tasks)
+2. context-package.json (smart context for execution environment)
+3. ANALYSIS_RESULTS.md (technical analysis and optimization strategies)
+4. Role-specific analyses (fallback for detailed specifications)
+
+## 4. Implementation Strategy
+
+### Execution Strategy
+**Execution Model**: [Sequential | Parallel | Phased | TDD Cycles]
+
+**Rationale**: [Why this execution model fits the project]
+
+**Parallelization Opportunities**:
+- [List independent workstreams]
+
+**Serialization Requirements**:
+- [List critical dependencies]
+
+### Architectural Approach
+**Key Architecture Decisions**:
+- [ADR references from role analyses]
+- [Justification for architecture patterns]
+
+**Integration Strategy**:
+- [How modules communicate]
+- [State management approach]
+
+### Key Dependencies
+**Task Dependency Graph**:
+```
+[High-level dependency visualization]
+```
+
+**Critical Path**: [Identify bottleneck tasks]
+
+### Testing Strategy
+**Testing Approach**:
+- Unit testing: [Tools, scope]
+- Integration testing: [Key integration points]
+- E2E testing: [Critical user flows]
+
+**Coverage Targets**:
+- Lines: ≥70%
+- Functions: ≥70%
+- Branches: ≥65%
+
+**Quality Gates**:
+- [CI/CD gates]
+- [Performance budgets]
+
+## 5. Task Breakdown Summary
+
+### Task Count
+**{N} tasks** (flat hierarchy | two-level hierarchy, sequential | parallel execution)
+
+### Task Structure
+- **IMPL-1**: [Main task title]
+- **IMPL-2**: [Main task title]
+...
+
+### Complexity Assessment
+- **High**: [List with rationale]
+- **Medium**: [List]
+- **Low**: [List]
+
+### Dependencies
+[Reference Section 4.3 for dependency graph]
+
+**Parallelization Opportunities**:
+- [Specific task groups that can run in parallel]
+
+## 6. Implementation Plan (Detailed Phased Breakdown)
+
+### Execution Strategy
+
+**Phase 1 (Weeks 1-2): [Phase Name]**
+- **Tasks**: IMPL-1, IMPL-2
+- **Deliverables**:
+  - [Specific deliverable 1]
+  - [Specific deliverable 2]
+- **Success Criteria**:
+  - [Measurable criterion]
+
+**Phase 2 (Weeks 3-N): [Phase Name]**
+...
+
+### Resource Requirements
+
+**Development Team**:
+- [Team composition and skills]
+
+**External Dependencies**:
+- [Third-party services, APIs]
+
+**Infrastructure**:
+- [Development, staging, production environments]
+
+## 7. Risk Assessment & Mitigation
+
+| Risk | Impact | Probability | Mitigation Strategy | Owner |
+|------|--------|-------------|---------------------|-------|
+| [Risk description] | High/Med/Low | High/Med/Low | [Strategy] | [Role] |
+
+**Critical Risks** (High impact + High probability):
+- [Risk 1]: [Detailed mitigation plan]
+
+**Monitoring Strategy**:
+- [How risks will be monitored]
+
+## 8. Success Criteria
+
+**Functional Completeness**:
+- [ ] All requirements from role analyses implemented
+- [ ] All acceptance criteria from task.json files met
+
+**Technical Quality**:
+- [ ] Test coverage ≥70%
+- [ ] Bundle size within budget
+- [ ] Performance targets met
+
+**Operational Readiness**:
+- [ ] CI/CD pipeline operational
+- [ ] Monitoring and logging configured
+- [ ] Documentation complete
+
+**Business Metrics**:
+- [ ] [Key business metrics from role analyses]
+
+## Template Usage Guidelines
+
+### When Generating IMPL_PLAN.md
+
+1. **Fill Frontmatter Variables**:
+   - Replace {session-id} with actual session ID
+   - Set workflow_type based on planning phase
+   - Update verification_history based on concept-verify results
+
+2. **Populate CCW Workflow Context**:
+   - Extract file/module counts from context-package.json
+   - Document phase progression based on completed workflow steps
+   - Update quality gate status (passed/skipped/pending)
+
+3. **Extract from Analysis Results**:
+   - Core objectives from ANALYSIS_RESULTS.md
+   - Technical approach and architecture decisions
+   - Risk assessment and mitigation strategies
+
+4. **Reference Brainstorming Artifacts**:
+   - List detected artifacts with correct paths
+   - Document artifact priority and usage strategy
+   - Map artifacts to specific tasks based on domain
+
+5. **Define Implementation Strategy**:
+   - Choose execution model (sequential/parallel/phased)
+   - Identify parallelization opportunities
+   - Document critical path and dependencies
+
+6. **Break Down Tasks**:
+   - List all task IDs and titles
+   - Assess complexity (high/medium/low)
+   - Create dependency graph visualization
+
+7. **Set Success Criteria**:
+   - Extract from role analyses
+   - Include measurable metrics
+   - Define quality gates
+
+### Validation Checklist
+
+Before finalizing IMPL_PLAN.md:
+- [ ] All frontmatter fields populated correctly
+- [ ] CCW workflow context reflects actual phase progression
+- [ ] Brainstorming artifacts correctly referenced
+- [ ] Task breakdown matches generated task JSONs
+- [ ] Dependencies are acyclic and logical
+- [ ] Success criteria are measurable
+- [ ] Risk assessment includes mitigation strategies
+- [ ] All {placeholder} variables replaced with actual values

.ccw/workflows/cli-templates/schemas/diagnosis-json-schema.json

@@ -0,0 +1,253 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Diagnosis Context Schema",
+  "description": "Bug diagnosis results from cli-explore-agent for root cause analysis",
+  "type": "object",
+  "required": [
+    "symptom",
+    "root_cause",
+    "affected_files",
+    "reproduction_steps",
+    "fix_hints",
+    "dependencies",
+    "constraints",
+    "clarification_needs",
+    "_metadata"
+  ],
+  "properties": {
+    "symptom": {
+      "type": "object",
+      "required": ["description", "error_message"],
+      "properties": {
+        "description": {
+          "type": "string",
+          "description": "Human-readable description of the bug symptoms"
+        },
+        "error_message": {
+          "type": ["string", "null"],
+          "description": "Exact error message if available, null if no specific error"
+        },
+        "stack_trace": {
+          "type": ["string", "null"],
+          "description": "Stack trace excerpt if available"
+        },
+        "frequency": {
+          "type": "string",
+          "enum": ["always", "intermittent", "rare", "unknown"],
+          "description": "How often the bug occurs"
+        },
+        "user_impact": {
+          "type": "string",
+          "description": "How the bug affects end users"
+        }
+      },
+      "description": "Observable symptoms and error manifestation"
+    },
+    "root_cause": {
+      "type": "object",
+      "required": ["file", "issue", "confidence"],
+      "properties": {
+        "file": {
+          "type": "string",
+          "description": "File path where the root cause is located"
+        },
+        "line_range": {
+          "type": "string",
+          "description": "Line range containing the bug (e.g., '45-60')"
+        },
+        "function": {
+          "type": "string",
+          "description": "Function or method name containing the bug"
+        },
+        "issue": {
+          "type": "string",
+          "description": "Description of what's wrong in the code"
+        },
+        "confidence": {
+          "type": "number",
+          "minimum": 0,
+          "maximum": 1,
+          "description": "Confidence score 0.0-1.0 (0.8+ high, 0.5-0.8 medium, <0.5 low)"
+        },
+        "introduced_by": {
+          "type": "string",
+          "description": "Commit hash or date when bug was introduced (if known)"
+        },
+        "category": {
+          "type": "string",
+          "enum": ["logic_error", "edge_case", "race_condition", "null_reference", "type_mismatch", "resource_leak", "validation", "integration", "configuration", "other"],
+          "description": "Bug category classification"
+        }
+      },
+      "description": "Root cause analysis with confidence score"
+    },
+    "affected_files": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "required": ["path", "relevance", "rationale", "change_type"],
+        "properties": {
+          "path": {
+            "type": "string",
+            "description": "File path relative to project root"
+          },
+          "relevance": {
+            "type": "number",
+            "minimum": 0,
+            "maximum": 1,
+            "description": "Relevance score 0.0-1.0 (0.7+ high, 0.5-0.7 medium, <0.5 low)"
+          },
+          "rationale": {
+            "type": "string",
+            "minLength": 10,
+            "description": "REQUIRED: Selection rationale explaining why this file is affected. Must be specific. Example: 'Contains handleLogin() at line 45 where null check is missing for token response' rather than 'Related to bug'"
+          },
+          "change_type": {
+            "type": "string",
+            "enum": ["fix_target", "needs_update", "test_coverage", "reference_only"],
+            "description": "Type of change needed: fix_target=contains the bug, needs_update=requires changes due to fix, test_coverage=tests to add/update, reference_only=understanding context"
+          },
+          "discovery_source": {
+            "type": "string",
+            "enum": ["bash-scan", "cli-analysis", "ace-search", "dependency-trace", "stack-trace", "manual"],
+            "description": "How the file was identified as affected"
+          },
+          "key_symbols": {
+            "type": "array",
+            "items": {"type": "string"},
+            "description": "Key symbols (functions, classes) in this file related to the bug"
+          }
+        },
+        "additionalProperties": false
+      },
+      "description": "Files affected by the bug. Every file MUST have structured rationale explaining why it is affected and what change is needed."
+    },
+    "reproduction_steps": {
+      "type": "array",
+      "items": {"type": "string"},
+      "minItems": 1,
+      "description": "Step-by-step instructions to reproduce the bug"
+    },
+    "fix_hints": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["description", "approach"],
+        "properties": {
+          "description": {
+            "type": "string",
+            "description": "What needs to be fixed"
+          },
+          "approach": {
+            "type": "string",
+            "description": "Suggested fix approach with specific guidance"
+          },
+          "code_example": {
+            "type": "string",
+            "description": "Example code snippet showing the fix pattern"
+          },
+          "risk": {
+            "type": "string",
+            "enum": ["low", "medium", "high"],
+            "description": "Risk level of implementing this fix"
+          }
+        }
+      },
+      "description": "Actionable fix suggestions from this diagnosis angle"
+    },
+    "dependencies": {
+      "type": "string",
+      "description": "External and internal dependencies relevant to the bug"
+    },
+    "constraints": {
+      "type": "string",
+      "description": "Technical constraints and limitations affecting the fix"
+    },
+    "related_issues": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "type": {
+            "type": "string",
+            "enum": ["similar_bug", "regression", "related_feature", "tech_debt"],
+            "description": "Relationship type"
+          },
+          "reference": {
+            "type": "string",
+            "description": "Issue ID, commit hash, or file reference"
+          },
+          "description": {
+            "type": "string",
+            "description": "Brief description of the relationship"
+          }
+        }
+      },
+      "description": "Related issues, regressions, or similar bugs found during diagnosis"
+    },
+    "clarification_needs": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["question", "context", "options"],
+        "properties": {
+          "question": {
+            "type": "string",
+            "description": "The clarification question to ask user"
+          },
+          "context": {
+            "type": "string",
+            "description": "Background context explaining why this clarification is needed"
+          },
+          "options": {
+            "type": "array",
+            "items": {"type": "string"},
+            "description": "Available options for user to choose from (2-4 options)"
+          }
+        }
+      },
+      "description": "Ambiguities requiring user input before fix planning"
+    },
+    "_metadata": {
+      "type": "object",
+      "required": ["timestamp", "bug_description", "source"],
+      "properties": {
+        "timestamp": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of diagnosis"
+        },
+        "bug_description": {
+          "type": "string",
+          "description": "Original bug description that triggered diagnosis"
+        },
+        "source": {
+          "type": "string",
+          "const": "cli-explore-agent",
+          "description": "Agent that performed diagnosis"
+        },
+        "diagnosis_angle": {
+          "type": "string",
+          "description": "Diagnosis angle (e.g., 'error-handling', 'dataflow', 'state-management')"
+        },
+        "diagnosis_index": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 4,
+          "description": "Diagnosis index (1-4) in parallel diagnosis set"
+        },
+        "total_diagnoses": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 4,
+          "description": "Total number of parallel diagnoses"
+        },
+        "duration_seconds": {
+          "type": "integer",
+          "description": "Diagnosis duration in seconds"
+        }
+      }
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/explore-json-schema.json

@@ -0,0 +1,157 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Exploration Context Schema",
+  "description": "Code exploration results from cli-explore-agent for task context gathering. Every file MUST include selection rationale.",
+  "type": "object",
+  "required": [
+    "project_structure",
+    "relevant_files",
+    "patterns",
+    "dependencies",
+    "integration_points",
+    "constraints",
+    "clarification_needs",
+    "_metadata"
+  ],
+  "properties": {
+    "project_structure": {
+      "type": "string",
+      "description": "Overall architecture description: module organization, layer structure, component relationships"
+    },
+    "relevant_files": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "required": ["path", "relevance", "rationale", "role"],
+        "properties": {
+          "path": {
+            "type": "string",
+            "description": "File path relative to project root"
+          },
+          "relevance": {
+            "type": "number",
+            "minimum": 0,
+            "maximum": 1,
+            "description": "Relevance score 0.0-1.0 (0.7+ high, 0.5-0.7 medium, <0.5 low)"
+          },
+          "rationale": {
+            "type": "string",
+            "minLength": 10,
+            "description": "REQUIRED: Selection rationale explaining why this file is relevant to the exploration topic. Must be specific (not generic). Example: 'Contains AuthService.login() which is the entry point for JWT token generation' rather than 'Related to auth'"
+          },
+          "role": {
+            "type": "string",
+            "enum": [
+              "modify_target",
+              "dependency",
+              "pattern_reference",
+              "test_target",
+              "type_definition",
+              "integration_point",
+              "config",
+              "context_only"
+            ],
+            "description": "File's role relative to the task: modify_target=needs changes, dependency=imported by targets, pattern_reference=demonstrates patterns to follow, test_target=tests needing update, type_definition=types/interfaces used, integration_point=where new code connects, config=configuration, context_only=understanding only"
+          },
+          "discovery_source": {
+            "type": "string",
+            "enum": ["bash-scan", "cli-analysis", "ace-search", "dependency-trace", "manual"],
+            "description": "How the file was discovered: bash-scan=structural scan (rg/find/tree), cli-analysis=Gemini/Qwen semantic analysis, ace-search=ACE context engine, dependency-trace=import/export graph traversal, manual=directly specified in task"
+          },
+          "key_symbols": {
+            "type": "array",
+            "items": {"type": "string"},
+            "description": "Key symbols (functions, classes, types) in this file relevant to the task. Example: ['AuthService', 'login', 'TokenPayload']"
+          }
+        },
+        "additionalProperties": false
+      },
+      "description": "Files relevant to the task. Every file MUST have structured rationale explaining its selection basis and role classification."
+    },
+    "patterns": {
+      "type": "string",
+      "description": "Existing code patterns, conventions, and styles found in the codebase"
+    },
+    "dependencies": {
+      "type": "string",
+      "description": "External and internal module dependencies relevant to the task"
+    },
+    "integration_points": {
+      "type": "string",
+      "description": "Where this task connects with existing code: APIs, hooks, events, shared state"
+    },
+    "constraints": {
+      "type": "string",
+      "description": "Technical constraints and limitations affecting implementation"
+    },
+    "clarification_needs": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["question", "context", "options"],
+        "properties": {
+          "question": {
+            "type": "string",
+            "description": "The clarification question to ask user"
+          },
+          "context": {
+            "type": "string",
+            "description": "Background context explaining why this clarification is needed"
+          },
+          "options": {
+            "type": "array",
+            "items": {"type": "string"},
+            "description": "Available options for user to choose from (2-4 options)"
+          },
+          "recommended": {
+            "type": "integer",
+            "minimum": 0,
+            "description": "Zero-based index of recommended option in the options array. Based on codebase patterns and best practices analysis."
+          }
+        }
+      },
+      "description": "Ambiguities requiring user input before planning"
+    },
+    "_metadata": {
+      "type": "object",
+      "required": ["timestamp", "task_description", "source"],
+      "properties": {
+        "timestamp": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of exploration"
+        },
+        "task_description": {
+          "type": "string",
+          "description": "Original task description that triggered exploration"
+        },
+        "source": {
+          "type": "string",
+          "const": "cli-explore-agent",
+          "description": "Agent that performed exploration"
+        },
+        "exploration_angle": {
+          "type": "string",
+          "description": "Agent-chosen exploration angle (e.g., 'architecture', 'security', 'dataflow')"
+        },
+        "exploration_index": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 4,
+          "description": "Exploration index (1-4) in parallel exploration set"
+        },
+        "total_explorations": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 4,
+          "description": "Total number of parallel explorations"
+        },
+        "duration_seconds": {
+          "type": "integer",
+          "description": "Exploration duration in seconds"
+        }
+      }
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/fix-plan-json-schema.json

@@ -0,0 +1,315 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Fix Plan Schema",
+  "description": "Bug fix plan from cli-lite-planning-agent or direct planning",
+  "type": "object",
+  "required": [
+    "summary",
+    "root_cause",
+    "strategy",
+    "tasks",
+    "estimated_time",
+    "recommended_execution",
+    "severity",
+    "risk_level",
+    "_metadata"
+  ],
+  "properties": {
+    "summary": {
+      "type": "string",
+      "description": "2-3 sentence overview of the fix plan"
+    },
+    "root_cause": {
+      "type": "string",
+      "description": "Consolidated root cause statement from all diagnoses"
+    },
+    "strategy": {
+      "type": "string",
+      "enum": ["immediate_patch", "comprehensive_fix", "refactor"],
+      "description": "Fix strategy: immediate_patch (minimal change), comprehensive_fix (proper solution), refactor (structural improvement)"
+    },
+    "tasks": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 5,
+      "items": {
+        "type": "object",
+        "required": ["id", "title", "scope", "action", "description", "implementation", "verification"],
+        "properties": {
+          "id": {
+            "type": "string",
+            "pattern": "^FIX[0-9]+$",
+            "description": "Task identifier (FIX1, FIX2, FIX3...)"
+          },
+          "title": {
+            "type": "string",
+            "description": "Task title (action verb + target, e.g., 'Fix token validation edge case')"
+          },
+          "scope": {
+            "type": "string",
+            "description": "Task scope: module path (src/auth/), feature name, or single file. Prefer module level."
+          },
+          "file": {
+            "type": "string",
+            "description": "Primary file (deprecated, use scope + modification_points instead)"
+          },
+          "action": {
+            "type": "string",
+            "enum": ["Fix", "Update", "Refactor", "Add", "Delete", "Configure"],
+            "description": "Primary action type"
+          },
+          "description": {
+            "type": "string",
+            "description": "What to fix (1-2 sentences)"
+          },
+          "modification_points": {
+            "type": "array",
+            "minItems": 1,
+            "items": {
+              "type": "object",
+              "required": ["file", "target", "change"],
+              "properties": {
+                "file": {
+                  "type": "string",
+                  "description": "File path within scope"
+                },
+                "target": {
+                  "type": "string",
+                  "description": "Function/class/line range (e.g., 'validateToken:45-60')"
+                },
+                "change": {
+                  "type": "string",
+                  "description": "Brief description of change"
+                }
+              }
+            },
+            "description": "All modification points for this fix task. Group related changes into one task."
+          },
+          "implementation": {
+            "type": "array",
+            "items": {"type": "string"},
+            "minItems": 2,
+            "maxItems": 5,
+            "description": "Step-by-step fix implementation guide"
+          },
+          "verification": {
+            "type": "array",
+            "items": {"type": "string"},
+            "minItems": 1,
+            "maxItems": 3,
+            "description": "Verification/test criteria to confirm fix works"
+          },
+          "reference": {
+            "type": "object",
+            "properties": {
+              "pattern": {
+                "type": "string",
+                "description": "Pattern name to follow"
+              },
+              "files": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Reference file paths to study"
+              },
+              "examples": {
+                "type": "string",
+                "description": "Specific guidance or example references"
+              }
+            },
+            "description": "Reference materials for fix implementation (optional)"
+          },
+          "depends_on": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "pattern": "^FIX[0-9]+$"
+            },
+            "description": "Task IDs this task depends on (e.g., ['FIX1'])"
+          },
+          "risk": {
+            "type": "string",
+            "enum": ["low", "medium", "high"],
+            "description": "Risk level of this specific fix task"
+          },
+          "cli_execution_id": {
+            "type": "string",
+            "pattern": "^[a-zA-Z0-9_-]+$",
+            "description": "Fixed CLI execution ID for this fix task (e.g., 'session-FIX1', 'bugfix-001-diagnosis')"
+          },
+          "cli_execution": {
+            "type": "object",
+            "properties": {
+              "strategy": {
+                "type": "string",
+                "enum": ["new", "resume", "fork", "merge_fork"],
+                "description": "CLI execution strategy: new (no deps), resume (1 dep, continue), fork (1 dep, branch), merge_fork (N deps, combine)"
+              },
+              "resume_from": {
+                "type": "string",
+                "description": "Parent task's cli_execution_id (for resume/fork strategies)"
+              },
+              "merge_from": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Multiple parents' cli_execution_ids (for merge_fork strategy)"
+              }
+            },
+            "description": "CLI execution strategy based on task dependencies"
+          }
+        }
+      },
+      "description": "Structured fix task breakdown (1-5 tasks)"
+    },
+    "flow_control": {
+      "type": "object",
+      "properties": {
+        "execution_order": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "phase": {
+                "type": "string",
+                "description": "Phase name (e.g., 'parallel-1', 'sequential-1')"
+              },
+              "tasks": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Task IDs in this phase"
+              },
+              "type": {
+                "type": "string",
+                "enum": ["parallel", "sequential"],
+                "description": "Execution type"
+              }
+            }
+          },
+          "description": "Ordered execution phases"
+        },
+        "exit_conditions": {
+          "type": "object",
+          "properties": {
+            "success": {
+              "type": "string",
+              "description": "Condition for successful fix completion"
+            },
+            "failure": {
+              "type": "string",
+              "description": "Condition that indicates fix failure"
+            }
+          },
+          "description": "Conditions for fix workflow termination"
+        }
+      },
+      "description": "Execution flow control (optional, auto-inferred from depends_on if not provided)"
+    },
+    "focus_paths": {
+      "type": "array",
+      "items": {"type": "string"},
+      "description": "Key file paths affected by this fix (aggregated from tasks)"
+    },
+    "test_strategy": {
+      "type": "object",
+      "properties": {
+        "scope": {
+          "type": "string",
+          "enum": ["unit", "integration", "e2e", "smoke", "full"],
+          "description": "Test scope to run after fix"
+        },
+        "specific_tests": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "Specific test files or patterns to run"
+        },
+        "manual_verification": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "Manual verification steps if automated tests not available"
+        }
+      },
+      "description": "Testing strategy for fix verification"
+    },
+    "rollback_plan": {
+      "type": "object",
+      "properties": {
+        "strategy": {
+          "type": "string",
+          "enum": ["git_revert", "feature_flag", "manual"],
+          "description": "Rollback strategy if fix fails"
+        },
+        "steps": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "Rollback steps"
+        }
+      },
+      "description": "Rollback plan if fix causes issues (optional, recommended for high severity)"
+    },
+    "estimated_time": {
+      "type": "string",
+      "description": "Total estimated fix time (e.g., '30 minutes', '2 hours')"
+    },
+    "recommended_execution": {
+      "type": "string",
+      "enum": ["Agent", "Codex"],
+      "description": "Recommended execution method based on complexity"
+    },
+    "severity": {
+      "type": "string",
+      "enum": ["Low", "Medium", "High", "Critical"],
+      "description": "Bug severity level"
+    },
+    "risk_level": {
+      "type": "string",
+      "enum": ["low", "medium", "high"],
+      "description": "Risk level of implementing the fix"
+    },
+    "_metadata": {
+      "type": "object",
+      "required": ["timestamp", "source"],
+      "properties": {
+        "timestamp": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of planning"
+        },
+        "source": {
+          "type": "string",
+          "enum": ["cli-lite-planning-agent", "direct-planning"],
+          "description": "Planning source"
+        },
+        "planning_mode": {
+          "type": "string",
+          "enum": ["direct", "agent-based"],
+          "description": "Planning execution mode"
+        },
+        "diagnosis_angles": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "Diagnosis angles used for context"
+        },
+        "duration_seconds": {
+          "type": "integer",
+          "description": "Planning duration in seconds"
+        }
+      }
+    }
+  },
+
+  "deprecated": true,
+  "deprecated_message": "Migrated to plan-overview-fix-schema.json (extends base) + task-schema.json.",
+  "migration_guide": {
+    "plan_level": "→ plan-overview-fix-schema.json (继承 base，含 fix_context)",
+    "task_level": "→ .task/FIX-*.json (task-schema.json)",
+    "field_mapping": {
+      "root_cause": "→ fix_context.root_cause",
+      "strategy": "→ fix_context.strategy",
+      "severity": "→ fix_context.severity",
+      "risk_level": "→ fix_context.risk_level",
+      "test_strategy": "→ plan-overview-fix-schema.test_strategy",
+      "rollback_plan": "→ plan-overview-fix-schema.rollback_plan",
+      "tasks[].verification[]": "→ convergence.criteria[]",
+      "tasks[].risk": "→ risks[] (结构化)"
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/plan-json-schema.json

@@ -0,0 +1,461 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Plan Object Schema",
+  "description": "Implementation plan from cli-lite-planning-agent or direct planning",
+  "type": "object",
+  "required": [
+    "summary",
+    "approach",
+    "tasks",
+    "estimated_time",
+    "recommended_execution",
+    "complexity",
+    "_metadata"
+  ],
+  "properties": {
+    "summary": {
+      "type": "string",
+      "description": "2-3 sentence overview of the implementation plan"
+    },
+    "approach": {
+      "type": "string",
+      "description": "High-level implementation strategy and methodology"
+    },
+    "tasks": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 10,
+      "items": {
+        "type": "object",
+        "required": ["id", "title", "scope", "action", "description", "implementation", "acceptance"],
+        "properties": {
+          "id": {
+            "type": "string",
+            "pattern": "^T[0-9]+$",
+            "description": "Task identifier (T1, T2, T3...)"
+          },
+          "title": {
+            "type": "string",
+            "description": "Task title (action verb + target module/feature)"
+          },
+          "scope": {
+            "type": "string",
+            "description": "Task scope: module path (src/auth/), feature name, or single file. Prefer module/feature level over single file."
+          },
+          "file": {
+            "type": "string",
+            "description": "Primary file (deprecated, use scope + modification_points instead)"
+          },
+          "action": {
+            "type": "string",
+            "enum": ["Create", "Update", "Implement", "Refactor", "Add", "Delete", "Configure", "Test", "Fix"],
+            "description": "Primary action type"
+          },
+          "description": {
+            "type": "string",
+            "description": "What to implement (1-2 sentences)"
+          },
+          "modification_points": {
+            "type": "array",
+            "minItems": 1,
+            "items": {
+              "type": "object",
+              "required": ["file", "target", "change"],
+              "properties": {
+                "file": {
+                  "type": "string",
+                  "description": "File path within scope"
+                },
+                "target": {
+                  "type": "string",
+                  "description": "Function/class/line range (e.g., 'validateToken:45-60')"
+                },
+                "change": {
+                  "type": "string",
+                  "description": "Brief description of change"
+                }
+              }
+            },
+            "description": "All modification points for this task. Group related changes (same feature/module) into one task with multiple modification_points."
+          },
+          "implementation": {
+            "type": "array",
+            "items": {"type": "string"},
+            "minItems": 2,
+            "maxItems": 7,
+            "description": "Step-by-step implementation guide"
+          },
+          "reference": {
+            "type": "object",
+            "properties": {
+              "pattern": {
+                "type": "string",
+                "description": "Pattern name to follow"
+              },
+              "files": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Reference file paths to study"
+              },
+              "examples": {
+                "type": "string",
+                "description": "Specific guidance or example references"
+              }
+            },
+            "description": "Reference materials for implementation (optional)"
+          },
+          "acceptance": {
+            "type": "array",
+            "items": {"type": "string"},
+            "minItems": 1,
+            "maxItems": 4,
+            "description": "Verification criteria (quantified, testable)"
+          },
+          "depends_on": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "pattern": "^T[0-9]+$"
+            },
+            "description": "Task IDs this task depends on (e.g., ['T1', 'T2'])"
+          },
+          "cli_execution_id": {
+            "type": "string",
+            "pattern": "^[a-zA-Z0-9_-]+$",
+            "description": "Fixed CLI execution ID for this task (e.g., 'session-T1', 'IMPL-001-analysis')"
+          },
+          "cli_execution": {
+            "type": "object",
+            "properties": {
+              "strategy": {
+                "type": "string",
+                "enum": ["new", "resume", "fork", "merge_fork"],
+                "description": "CLI execution strategy: new (no deps), resume (1 dep, continue), fork (1 dep, branch), merge_fork (N deps, combine)"
+              },
+              "resume_from": {
+                "type": "string",
+                "description": "Parent task's cli_execution_id (for resume/fork strategies)"
+              },
+              "merge_from": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Multiple parents' cli_execution_ids (for merge_fork strategy)"
+              }
+            },
+            "description": "CLI execution strategy based on task dependencies"
+          },
+          "rationale": {
+            "type": "object",
+            "properties": {
+              "chosen_approach": {
+                "type": "string",
+                "description": "The selected implementation approach and why it was chosen"
+              },
+              "alternatives_considered": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Alternative approaches that were considered but not chosen"
+              },
+              "decision_factors": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Key factors that influenced the decision (performance, maintainability, cost, etc.)"
+              },
+              "tradeoffs": {
+                "type": "string",
+                "description": "Known tradeoffs of the chosen approach"
+              }
+            },
+            "description": "Design rationale explaining WHY this approach was chosen (required for Medium/High complexity)"
+          },
+          "verification": {
+            "type": "object",
+            "properties": {
+              "unit_tests": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "List of unit test names/descriptions to create"
+              },
+              "integration_tests": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "List of integration test names/descriptions to create"
+              },
+              "manual_checks": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Manual verification steps with specific actions"
+              },
+              "success_metrics": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Quantified metrics for success (e.g., 'Response time <200ms', 'Coverage >80%')"
+              }
+            },
+            "description": "Detailed verification steps beyond acceptance criteria (required for Medium/High complexity)"
+          },
+          "risks": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "required": ["description", "probability", "impact", "mitigation"],
+              "properties": {
+                "description": {
+                  "type": "string",
+                  "description": "Description of the risk"
+                },
+                "probability": {
+                  "type": "string",
+                  "enum": ["Low", "Medium", "High"],
+                  "description": "Likelihood of the risk occurring"
+                },
+                "impact": {
+                  "type": "string",
+                  "enum": ["Low", "Medium", "High"],
+                  "description": "Impact severity if the risk occurs"
+                },
+                "mitigation": {
+                  "type": "string",
+                  "description": "Strategy to mitigate or prevent the risk"
+                },
+                "fallback": {
+                  "type": "string",
+                  "description": "Alternative approach if mitigation fails"
+                }
+              }
+            },
+            "description": "Risk assessment and mitigation strategies (required for High complexity)"
+          },
+          "code_skeleton": {
+            "type": "object",
+            "properties": {
+              "interfaces": {
+                "type": "array",
+                "items": {
+                  "type": "object",
+                  "properties": {
+                    "name": {"type": "string"},
+                    "definition": {"type": "string"},
+                    "purpose": {"type": "string"}
+                  }
+                },
+                "description": "Key interface/type definitions"
+              },
+              "key_functions": {
+                "type": "array",
+                "items": {
+                  "type": "object",
+                  "properties": {
+                    "signature": {"type": "string"},
+                    "purpose": {"type": "string"},
+                    "returns": {"type": "string"}
+                  }
+                },
+                "description": "Critical function signatures"
+              },
+              "classes": {
+                "type": "array",
+                "items": {
+                  "type": "object",
+                  "properties": {
+                    "name": {"type": "string"},
+                    "purpose": {"type": "string"},
+                    "methods": {
+                      "type": "array",
+                      "items": {"type": "string"}
+                    }
+                  }
+                },
+                "description": "Key class structures"
+              }
+            },
+            "description": "Code skeleton with interface/function signatures (required for High complexity)"
+          }
+        }
+      },
+      "description": "Structured task breakdown (1-10 tasks)"
+    },
+    "data_flow": {
+      "type": "object",
+      "properties": {
+        "diagram": {
+          "type": "string",
+          "description": "ASCII/text representation of data flow (e.g., 'A → B → C')"
+        },
+        "stages": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "required": ["stage", "input", "output", "component"],
+            "properties": {
+              "stage": {
+                "type": "string",
+                "description": "Stage name (e.g., 'Extraction', 'Processing', 'Storage')"
+              },
+              "input": {
+                "type": "string",
+                "description": "Input data format/type"
+              },
+              "output": {
+                "type": "string",
+                "description": "Output data format/type"
+              },
+              "component": {
+                "type": "string",
+                "description": "Component/module handling this stage"
+              },
+              "transformations": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Data transformations applied in this stage"
+              }
+            }
+          },
+          "description": "Detailed data flow stages"
+        },
+        "dependencies": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "External dependencies or data sources"
+        }
+      },
+      "description": "Global data flow design showing how data moves through the system (required for High complexity)"
+    },
+    "design_decisions": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["decision", "rationale"],
+        "properties": {
+          "decision": {
+            "type": "string",
+            "description": "The design decision made"
+          },
+          "rationale": {
+            "type": "string",
+            "description": "Why this decision was made"
+          },
+          "tradeoff": {
+            "type": "string",
+            "description": "What was traded off for this decision"
+          },
+          "alternatives": {
+            "type": "array",
+            "items": {"type": "string"},
+            "description": "Alternatives that were considered"
+          }
+        }
+      },
+      "description": "Global design decisions that affect the entire plan"
+    },
+    "flow_control": {
+      "type": "object",
+      "properties": {
+        "execution_order": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "phase": {
+                "type": "string",
+                "description": "Phase name (e.g., 'parallel-1', 'sequential-1')"
+              },
+              "tasks": {
+                "type": "array",
+                "items": {"type": "string"},
+                "description": "Task IDs in this phase"
+              },
+              "type": {
+                "type": "string",
+                "enum": ["parallel", "sequential"],
+                "description": "Execution type"
+              }
+            }
+          },
+          "description": "Ordered execution phases"
+        },
+        "exit_conditions": {
+          "type": "object",
+          "properties": {
+            "success": {
+              "type": "string",
+              "description": "Condition for successful completion"
+            },
+            "failure": {
+              "type": "string",
+              "description": "Condition that indicates failure"
+            }
+          },
+          "description": "Conditions for workflow termination"
+        }
+      },
+      "description": "Execution flow control (optional, auto-inferred from depends_on if not provided)"
+    },
+    "focus_paths": {
+      "type": "array",
+      "items": {"type": "string"},
+      "description": "Key file paths affected by this plan (aggregated from tasks)"
+    },
+    "estimated_time": {
+      "type": "string",
+      "description": "Total estimated implementation time (e.g., '30 minutes', '2 hours')"
+    },
+    "recommended_execution": {
+      "type": "string",
+      "enum": ["Agent", "Codex"],
+      "description": "Recommended execution method based on complexity"
+    },
+    "complexity": {
+      "type": "string",
+      "enum": ["Low", "Medium", "High"],
+      "description": "Task complexity level"
+    },
+    "_metadata": {
+      "type": "object",
+      "required": ["timestamp", "source"],
+      "properties": {
+        "timestamp": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of planning"
+        },
+        "source": {
+          "type": "string",
+          "enum": ["cli-lite-planning-agent", "direct-planning"],
+          "description": "Planning source"
+        },
+        "planning_mode": {
+          "type": "string",
+          "enum": ["direct", "agent-based"],
+          "description": "Planning execution mode"
+        },
+        "exploration_angles": {
+          "type": "array",
+          "items": {"type": "string"},
+          "description": "Exploration angles used for context"
+        },
+        "duration_seconds": {
+          "type": "integer",
+          "description": "Planning duration in seconds"
+        }
+      }
+    }
+  },
+
+  "deprecated": true,
+  "deprecated_message": "Migrated to plan-overview-base-schema.json + task-schema.json (PLANNING 区块).",
+  "migration_guide": {
+    "plan_level": "→ plan-overview-base-schema.json",
+    "task_level": "→ .task/TASK-*.json (task-schema.json)",
+    "field_mapping": {
+      "tasks[].modification_points": "→ files[].change (合并入 files)",
+      "tasks[].reference": "→ reference (直接迁移)",
+      "tasks[].rationale": "→ rationale (直接迁移)",
+      "tasks[].verification": "→ test.manual_checks + test.success_metrics (合并入 test)",
+      "tasks[].risks": "→ risks (直接迁移)",
+      "tasks[].code_skeleton": "→ code_skeleton (直接迁移)",
+      "tasks[].acceptance": "→ convergence.criteria (已删除别名，直接用 convergence)",
+      "tasks[].cli_execution_id": "→ cli_execution.id (已存在)"
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/plan-overview-base-schema.json

@@ -0,0 +1,210 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "plan-overview-base-schema.json",
+  "title": "Plan Overview Base Schema",
+  "description": "计划概览基础 schema — 所有计划类型共享字段。Feature 类型直接使用此 schema，其他类型 (fix/tdd/review) 通过 allOf 继承并扩展。",
+  "type": "object",
+  "required": ["summary", "approach", "task_ids", "task_count", "_metadata"],
+
+  "properties": {
+    "summary": {
+      "type": "string",
+      "description": "2-3 句计划概述"
+    },
+    "approach": {
+      "type": "string",
+      "description": "高层实施策略和方法论"
+    },
+    "task_ids": {
+      "type": "array",
+      "items": { "type": "string" },
+      "minItems": 1,
+      "description": "引用 .task/ 下的任务 ID 列表 (如 ['TASK-001', 'TASK-002'])"
+    },
+    "task_count": {
+      "type": "integer",
+      "minimum": 1,
+      "description": "任务数量 (应等于 task_ids.length)"
+    },
+
+    "complexity": {
+      "type": "string",
+      "enum": ["Low", "Medium", "High"],
+      "description": "计划复杂度"
+    },
+    "estimated_time": {
+      "type": "string",
+      "description": "总估算时间 (如 '30 minutes', '2 hours')"
+    },
+    "recommended_execution": {
+      "type": "string",
+      "enum": ["Agent", "Codex"],
+      "description": "推荐执行方式"
+    },
+
+    "data_flow": {
+      "type": "object",
+      "properties": {
+        "diagram": {
+          "type": "string",
+          "description": "ASCII/文本形式的数据流图 (如 'A → B → C')"
+        },
+        "stages": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "required": ["stage", "input", "output", "component"],
+            "properties": {
+              "stage": {
+                "type": "string",
+                "description": "阶段名称"
+              },
+              "input": {
+                "type": "string",
+                "description": "输入数据格式/类型"
+              },
+              "output": {
+                "type": "string",
+                "description": "输出数据格式/类型"
+              },
+              "component": {
+                "type": "string",
+                "description": "处理该阶段的组件/模块"
+              },
+              "transformations": {
+                "type": "array",
+                "items": { "type": "string" },
+                "description": "该阶段的数据转换"
+              }
+            }
+          },
+          "description": "详细数据流阶段"
+        },
+        "dependencies": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "外部依赖或数据源"
+        }
+      },
+      "description": "全局数据流设计"
+    },
+
+    "design_decisions": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["decision", "rationale"],
+        "properties": {
+          "decision": {
+            "type": "string",
+            "description": "设计决策"
+          },
+          "rationale": {
+            "type": "string",
+            "description": "决策原因"
+          },
+          "tradeoff": {
+            "type": "string",
+            "description": "权衡取舍"
+          },
+          "alternatives": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "考虑过的替代方案"
+          }
+        }
+      },
+      "description": "影响整个计划的全局设计决策"
+    },
+
+
+    "shared_context": {
+      "type": "object",
+      "description": "Project-level shared context (tech stack, conventions).",
+      "properties": {
+        "tech_stack": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "技术栈列表"
+        },
+        "conventions": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "编码约定"
+        },
+        "auth_strategy": {
+          "type": "string",
+          "description": "认证策略"
+        }
+      },
+      "additionalProperties": true
+    },
+
+    "_metadata": {
+      "type": "object",
+      "required": ["timestamp", "source", "plan_type"],
+      "properties": {
+        "timestamp": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 规划时间戳"
+        },
+        "source": {
+          "type": "string",
+          "enum": ["cli-lite-planning-agent", "direct-planning", "action-planning-agent", "review-cycle-agent", "issue-plan-agent", "tdd-planning-agent"],
+          "description": "规划来源 — 标识产生此 plan 的实际规划引擎"
+        },
+        "planning_mode": {
+          "type": "string",
+          "enum": ["direct", "agent-based"],
+          "description": "规划执行模式"
+        },
+        "plan_type": {
+          "type": "string",
+          "enum": ["feature", "fix", "tdd", "review", "collaborative", "requirement"],
+          "description": "计划类型 — 消费端据此选择对应的扩展 schema 校验"
+        },
+        "schema_version": {
+          "type": "string",
+          "default": "2.0",
+          "description": "Schema 版本"
+        },
+        "exploration_angles": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "用于上下文的探索角度"
+        },
+        "duration_seconds": {
+          "type": "integer",
+          "description": "规划耗时 (秒)"
+        }
+      }
+    }
+  },
+
+  "additionalProperties": true,
+
+  "_extension_guide": {
+    "description": "扩展指南 — 通过 allOf + $ref 继承此 base schema",
+    "available_extensions": {
+      "fix": "plan-overview-fix-schema.json — fix_context, test_strategy, rollback_plan",
+      "tdd": "(未来) plan-overview-tdd-schema.json — tdd_cycles, coverage_targets, phase_requirements",
+      "review": "(未来) plan-overview-review-schema.json — review_dimensions, finding_summary"
+    },
+    "feature_note": "feature 类型直接使用此 base schema，无需额外扩展"
+  },
+
+  "_field_migration_from_plan_json": {
+    "summary": "直接迁移",
+    "approach": "直接迁移",
+    "tasks": "→ task_ids[] (引用 .task/ 下的独立文件)",
+    "complexity": "直接迁移",
+    "estimated_time": "直接迁移",
+    "recommended_execution": "直接迁移",
+    "data_flow": "直接迁移",
+    "design_decisions": "直接迁移",
+    "flow_control": "→ 删除 (由引擎从 task depends_on + parallel_group 自动推断)",
+    "focus_paths": "→ 删除 (由引擎从 task focus_paths / files[].path 聚合)",
+    "_metadata": "扩展 (新增 plan_type, schema_version)"
+  }
+}

.ccw/workflows/cli-templates/schemas/plan-overview-fix-schema.json

@@ -0,0 +1,103 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "plan-overview-fix-schema.json",
+  "title": "Fix Plan Overview Schema",
+  "description": "Fix 计划概览 — 继承 base + fix 专属字段。_metadata.plan_type 必须为 'fix'。",
+  "allOf": [
+    { "$ref": "plan-overview-base-schema.json" }
+  ],
+  "required": ["fix_context"],
+  "properties": {
+    "fix_context": {
+      "type": "object",
+      "required": ["root_cause", "strategy", "severity", "risk_level"],
+      "properties": {
+        "root_cause": {
+          "type": "string",
+          "description": "根因描述 (从 fix-plan-json-schema.root_cause 迁移)"
+        },
+        "strategy": {
+          "type": "string",
+          "enum": ["immediate_patch", "comprehensive_fix", "refactor"],
+          "description": "修复策略 (从 fix-plan-json-schema.strategy 迁移)"
+        },
+        "severity": {
+          "type": "string",
+          "enum": ["Low", "Medium", "High", "Critical"],
+          "description": "Bug 严重等级 (从 fix-plan-json-schema.severity 迁移)"
+        },
+        "risk_level": {
+          "type": "string",
+          "enum": ["low", "medium", "high"],
+          "description": "修复风险等级 (从 fix-plan-json-schema.risk_level 迁移)"
+        }
+      },
+      "additionalProperties": false,
+      "description": "Fix 专属上下文 — 整合原 fix-plan-json-schema 的顶层 fix 字段"
+    },
+
+    "test_strategy": {
+      "type": "object",
+      "properties": {
+        "scope": {
+          "type": "string",
+          "enum": ["unit", "integration", "e2e", "smoke", "full"],
+          "description": "修复后的测试范围"
+        },
+        "specific_tests": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "需运行的特定测试文件或模式"
+        },
+        "manual_verification": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "手动验证步骤 (无自动化测试时)"
+        }
+      },
+      "additionalProperties": false,
+      "description": "修复验证测试策略 (从 fix-plan-json-schema.test_strategy 迁移)"
+    },
+
+    "rollback_plan": {
+      "type": "object",
+      "properties": {
+        "strategy": {
+          "type": "string",
+          "enum": ["git_revert", "feature_flag", "manual"],
+          "description": "回滚策略"
+        },
+        "steps": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "回滚步骤"
+        }
+      },
+      "additionalProperties": false,
+      "description": "回滚计划 (从 fix-plan-json-schema.rollback_plan 迁移)"
+    },
+
+    "_metadata": {
+      "type": "object",
+      "properties": {
+        "diagnosis_angles": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "诊断角度 (fix 特有，从 fix-plan-json-schema._metadata.diagnosis_angles 迁移)"
+        }
+      },
+      "description": "Fix 扩展的 metadata 字段 (与 base _metadata 合并)"
+    }
+  },
+
+  "_field_migration_from_fix_plan_json": {
+    "root_cause": "→ fix_context.root_cause",
+    "strategy": "→ fix_context.strategy",
+    "severity": "→ fix_context.severity",
+    "risk_level": "→ fix_context.risk_level",
+    "test_strategy": "直接迁移",
+    "rollback_plan": "直接迁移",
+    "tasks": "→ task_ids[] (引用 .task/ 下的独立文件)",
+    "_metadata.diagnosis_angles": "直接迁移"
+  }
+}

.ccw/workflows/cli-templates/schemas/plan-verify-agent-schema.json

@@ -0,0 +1,51 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Plan Verification Agent Schema",
+  "description": "Defines dimensions, severity rules, and CLI templates for plan verification agent",
+
+  "dimensions": {
+    "A": { "name": "User Intent Alignment", "tier": 1, "severity": "CRITICAL",
+           "checks": ["Goal Alignment", "Scope Drift", "Success Criteria Match", "Intent Conflicts"] },
+    "B": { "name": "Requirements Coverage", "tier": 1, "severity": "CRITICAL",
+           "checks": ["Orphaned Requirements", "Unmapped Tasks", "NFR Coverage Gaps"] },
+    "C": { "name": "Consistency Validation", "tier": 1, "severity": "CRITICAL",
+           "checks": ["Requirement Conflicts", "Architecture Drift", "Terminology Drift", "Data Model Inconsistency"] },
+    "D": { "name": "Dependency Integrity", "tier": 2, "severity": "HIGH",
+           "checks": ["Circular Dependencies", "Missing Dependencies", "Broken Dependencies", "Logical Ordering"] },
+    "E": { "name": "Synthesis Alignment", "tier": 2, "severity": "HIGH",
+           "checks": ["Priority Conflicts", "Success Criteria Mismatch", "Risk Mitigation Gaps"] },
+    "F": { "name": "Task Specification Quality", "tier": 3, "severity": "MEDIUM",
+           "checks": ["Ambiguous Focus Paths", "Underspecified Acceptance", "Missing Artifacts", "Weak Flow Control"] },
+    "G": { "name": "Duplication Detection", "tier": 4, "severity": "LOW",
+           "checks": ["Overlapping Task Scope", "Redundant Coverage"] },
+    "H": { "name": "Feasibility Assessment", "tier": 4, "severity": "LOW",
+           "checks": ["Complexity Misalignment", "Resource Conflicts", "Skill Gap Risks"] },
+    "I": { "name": "Constraints Compliance", "tier": 1, "severity": "CRITICAL",
+           "checks": ["Consolidated Constraints Violation", "Phase Constraint Ignored", "User Constraint Override"] },
+    "J": { "name": "N+1 Context Validation", "tier": 2, "severity": "HIGH",
+           "checks": ["Deferred Item Included", "Decision Contradiction", "Revisit Flag Ignored"] }
+  },
+
+  "tiers": {
+    "1": { "dimensions": ["A", "B", "C", "I"], "priority": "CRITICAL", "limit": null, "rule": "analysis-review-architecture" },
+    "2": { "dimensions": ["D", "E", "J"], "priority": "HIGH", "limit": 15, "rule": "analysis-diagnose-bug-root-cause" },
+    "3": { "dimensions": ["F"], "priority": "MEDIUM", "limit": 20, "rule": "analysis-analyze-code-patterns" },
+    "4": { "dimensions": ["G", "H"], "priority": "LOW", "limit": 15, "rule": "analysis-analyze-code-patterns" }
+  },
+
+  "severity_rules": {
+    "CRITICAL": ["User intent violation", "Synthesis authority violation", "Zero coverage", "Circular/broken deps", "Constraint violation"],
+    "HIGH": ["NFR gaps", "Priority conflicts", "Missing risk mitigation", "Deferred item included", "Decision contradiction"],
+    "MEDIUM": ["Terminology drift", "Missing refs", "Weak flow control"],
+    "LOW": ["Style improvements", "Minor redundancy"]
+  },
+
+  "quality_gate": {
+    "BLOCK_EXECUTION": { "condition": "critical > 0", "emoji": "🛑" },
+    "PROCEED_WITH_FIXES": { "condition": "critical == 0 && high > 0", "emoji": "⚠️" },
+    "PROCEED_WITH_CAUTION": { "condition": "critical == 0 && high == 0 && medium > 0", "emoji": "✅" },
+    "PROCEED": { "condition": "only low or none", "emoji": "✅" }
+  },
+
+  "token_budget": { "total_findings": 50, "early_exit": "CRITICAL > 0 in Tier 1 → skip Tier 3-4" }
+}

.ccw/workflows/cli-templates/schemas/project-guidelines-schema.json

@@ -0,0 +1,141 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Project Guidelines Schema",
+  "description": "Legacy schema - project guidelines now managed by spec system (`ccw spec load --dimension specs`)",
+  "type": "object",
+  "required": ["conventions", "constraints", "_metadata"],
+  "properties": {
+    "conventions": {
+      "type": "object",
+      "description": "Coding conventions and standards",
+      "required": ["coding_style", "naming_patterns", "file_structure", "documentation"],
+      "properties": {
+        "coding_style": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Coding style rules (e.g., 'Use strict TypeScript mode', 'Prefer const over let')"
+        },
+        "naming_patterns": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Naming conventions (e.g., 'Use camelCase for variables', 'Use PascalCase for components')"
+        },
+        "file_structure": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "File organization rules (e.g., 'One component per file', 'Tests alongside source files')"
+        },
+        "documentation": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Documentation requirements (e.g., 'JSDoc for public APIs', 'README for each module')"
+        }
+      }
+    },
+    "constraints": {
+      "type": "object",
+      "description": "Technical constraints and boundaries",
+      "required": ["architecture", "tech_stack", "performance", "security"],
+      "properties": {
+        "architecture": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Architecture constraints (e.g., 'No circular dependencies', 'Services must be stateless')"
+        },
+        "tech_stack": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Technology constraints (e.g., 'No new dependencies without review', 'Use native fetch over axios')"
+        },
+        "performance": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Performance requirements (e.g., 'API response < 200ms', 'Bundle size < 500KB')"
+        },
+        "security": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "Security requirements (e.g., 'Sanitize all user input', 'No secrets in code')"
+        }
+      }
+    },
+    "quality_rules": {
+      "type": "array",
+      "description": "Enforceable quality rules",
+      "items": {
+        "type": "object",
+        "required": ["rule", "scope"],
+        "properties": {
+          "rule": {
+            "type": "string",
+            "description": "The quality rule statement"
+          },
+          "scope": {
+            "type": "string",
+            "description": "Where the rule applies (e.g., 'all', 'src/**', 'tests/**')"
+          },
+          "enforced_by": {
+            "type": "string",
+            "description": "How the rule is enforced (e.g., 'eslint', 'pre-commit', 'code-review')"
+          }
+        }
+      }
+    },
+    "learnings": {
+      "type": "array",
+      "description": "Project learnings captured from workflow sessions",
+      "items": {
+        "type": "object",
+        "required": ["date", "insight"],
+        "properties": {
+          "date": {
+            "type": "string",
+            "format": "date",
+            "description": "Date the learning was captured (YYYY-MM-DD)"
+          },
+          "session_id": {
+            "type": "string",
+            "description": "WFS session ID where the learning originated"
+          },
+          "insight": {
+            "type": "string",
+            "description": "The learning or insight captured"
+          },
+          "context": {
+            "type": "string",
+            "description": "Additional context about when/why this learning applies"
+          },
+          "category": {
+            "type": "string",
+            "enum": ["architecture", "performance", "security", "testing", "workflow", "other"],
+            "description": "Category of the learning"
+          }
+        }
+      }
+    },
+    "_metadata": {
+      "type": "object",
+      "required": ["created_at", "version"],
+      "properties": {
+        "created_at": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of creation"
+        },
+        "version": {
+          "type": "string",
+          "description": "Schema version (e.g., '1.0.0')"
+        },
+        "last_updated": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO 8601 timestamp of last update"
+        },
+        "updated_by": {
+          "type": "string",
+          "description": "Who/what last updated the file (e.g., 'user', 'workflow:session:solidify')"
+        }
+      }
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/solution-schema.json

@@ -0,0 +1,225 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Issue Solution Schema",
+  "description": "Schema for solution registered to an issue",
+  "type": "object",
+  "required": ["id", "tasks", "is_bound", "created_at"],
+  "properties": {
+    "id": {
+      "type": "string",
+      "description": "Unique solution identifier: SOL-{issue-id}-{4-char-uid} where uid is 4 alphanumeric chars",
+      "pattern": "^SOL-.+-[a-z0-9]{4}$",
+      "examples": ["SOL-GH-123-a7x9", "SOL-ISS-20251229-001-b2k4"]
+    },
+    "description": {
+      "type": "string",
+      "description": "High-level summary of the solution"
+    },
+    "approach": {
+      "type": "string",
+      "description": "Technical approach or strategy"
+    },
+    "tasks": {
+      "type": "array",
+      "description": "Task breakdown for this solution",
+      "items": {
+        "type": "object",
+        "required": ["id", "title", "scope", "action", "implementation"],
+        "properties": {
+          "id": {
+            "type": "string",
+            "pattern": "^T[0-9]+$"
+          },
+          "title": {
+            "type": "string",
+            "description": "Action verb + target"
+          },
+          "scope": {
+            "type": "string",
+            "description": "Module path or feature area"
+          },
+          "action": {
+            "type": "string",
+            "enum": ["Create", "Update", "Implement", "Refactor", "Add", "Delete", "Configure", "Test", "Fix"]
+          },
+          "description": {
+            "type": "string",
+            "description": "1-2 sentences describing what to implement"
+          },
+          "files": {
+            "type": "array",
+            "description": "Files affected by this task (preferred over modification_points)",
+            "items": {
+              "type": "object",
+              "required": ["path"],
+              "properties": {
+                "path": { "type": "string", "description": "File path relative to project root" },
+                "action": { "type": "string", "enum": ["modify", "create", "delete"], "description": "Type of file operation" },
+                "target": { "type": "string", "description": "Target symbol or location within file" },
+                "change": { "type": "string", "description": "Description of the change" },
+                "changes": { "type": "array", "items": { "type": "string" }, "description": "Multiple changes to the file" },
+                "conflict_risk": { "type": "string", "enum": ["low", "medium", "high"], "description": "Risk of merge conflict" }
+              }
+            }
+          },
+          "modification_points": {
+            "type": "array",
+            "deprecated": true,
+            "description": "DEPRECATED: Use 'files' instead. Legacy field for backward compatibility.",
+            "items": {
+              "type": "object",
+              "properties": {
+                "file": { "type": "string" },
+                "target": { "type": "string" },
+                "change": { "type": "string" }
+              }
+            }
+          },
+          "implementation": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "Step-by-step implementation guide"
+          },
+          "test": {
+            "type": "object",
+            "description": "Test requirements",
+            "properties": {
+              "unit": { "type": "array", "items": { "type": "string" } },
+              "integration": { "type": "array", "items": { "type": "string" } },
+              "commands": { "type": "array", "items": { "type": "string" } },
+              "coverage_target": { "type": "number" },
+              "manual_checks": { "type": "array", "items": { "type": "string" }, "description": "Manual verification steps" },
+              "success_metrics": { "type": "array", "items": { "type": "string" }, "description": "Success metrics for the task" }
+            }
+          },
+          "regression": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "Regression check points"
+          },
+          "convergence": {
+            "type": "object",
+            "description": "Convergence criteria & verification (preferred over acceptance)",
+            "required": ["criteria"],
+            "properties": {
+              "criteria": { "type": "array", "items": { "type": "string" } },
+              "verification": {
+                "oneOf": [
+                  { "type": "string" },
+                  { "type": "array", "items": { "type": "string" } }
+                ]
+              },
+              "definition_of_done": { "type": "string" }
+            }
+          },
+          "acceptance": {
+            "type": "object",
+            "deprecated": true,
+            "description": "DEPRECATED: Use 'convergence' instead. Legacy field for backward compatibility.",
+            "properties": {
+              "criteria": { "type": "array", "items": { "type": "string" } },
+              "verification": { "type": "array", "items": { "type": "string" } },
+              "manual_checks": { "type": "array", "items": { "type": "string" } }
+            }
+          },
+          "commit": {
+            "type": "object",
+            "description": "Commit specification",
+            "properties": {
+              "type": { "type": "string", "enum": ["feat", "fix", "refactor", "test", "docs", "chore"] },
+              "scope": { "type": "string" },
+              "message_template": { "type": "string" },
+              "breaking": { "type": "boolean" }
+            }
+          },
+          "depends_on": {
+            "type": "array",
+            "items": { "type": "string" },
+            "default": [],
+            "description": "Task IDs this task depends on"
+          },
+          "estimated_minutes": {
+            "type": "integer",
+            "description": "DEPRECATED: Use 'effort' instead. Estimated time to complete."
+          },
+          "effort": {
+            "type": "string",
+            "enum": ["small", "medium", "large", "xlarge"],
+            "description": "Effort estimate for the task"
+          },
+          "status": {
+            "type": "string",
+            "description": "Task status (optional, for tracking)"
+          },
+          "priority": {
+            "oneOf": [
+              { "type": "string", "enum": ["critical", "high", "medium", "low"] },
+              { "type": "integer", "minimum": 1, "maximum": 5 }
+            ],
+            "default": "medium",
+            "description": "Task priority. Prefer string enum; integer 1-5 accepted for backward compatibility."
+          }
+        },
+        "anyOf": [
+          { "required": ["convergence"] },
+          { "required": ["acceptance"] }
+        ],
+        "_migration": {
+          "description": "Field migration mapping from legacy to current format",
+          "mappings": {
+            "modification_points[].file": "files[].path",
+            "modification_points[].target": "files[].target",
+            "modification_points[].change": "files[].change",
+            "acceptance.criteria": "convergence.criteria",
+            "acceptance.verification": "convergence.verification",
+            "acceptance.manual_checks": "test.manual_checks",
+            "priority (integer 1-5)": "priority (string enum)",
+            "estimated_minutes": "effort"
+          }
+        }
+      }
+    },
+    "exploration_context": {
+      "type": "object",
+      "description": "ACE exploration results",
+      "properties": {
+        "project_structure": { "type": "string" },
+        "relevant_files": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "patterns": { "type": "string" },
+        "integration_points": { "type": "string" }
+      }
+    },
+    "analysis": {
+      "type": "object",
+      "description": "Solution risk assessment",
+      "properties": {
+        "risk": { "type": "string", "enum": ["low", "medium", "high"] },
+        "impact": { "type": "string", "enum": ["low", "medium", "high"] },
+        "complexity": { "type": "string", "enum": ["low", "medium", "high"] }
+      }
+    },
+    "score": {
+      "type": "number",
+      "minimum": 0,
+      "maximum": 1,
+      "description": "Solution quality score (0.0-1.0)"
+    },
+    "is_bound": {
+      "type": "boolean",
+      "default": false,
+      "description": "Whether this solution is bound to the issue"
+    },
+    "created_at": {
+      "type": "string",
+      "format": "date-time"
+    },
+    "bound_at": {
+      "type": "string",
+      "format": "date-time",
+      "description": "When this solution was bound to the issue"
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/task-schema.json

@@ -0,0 +1,586 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "task-schema.json",
+  "title": "Unified Task JSON Schema",
+  "description": "统一任务定义 schema v1.0 — 每个任务一个独立 JSON 文件，自包含所有执行所需信息。融合 Unified JSONL (convergence)、6-field Task JSON (execution_config)、Solution Schema (modification_points) 三者优势。",
+  "type": "object",
+  "required": ["id", "title", "description", "depends_on", "convergence"],
+
+  "properties": {
+
+    "_comment_IDENTITY": "IDENTITY 区块 (必填) — 任务基本信息",
+    "id": {
+      "type": "string",
+      "description": "任务ID，前缀由生产者决定 (TASK-001 / IMPL-001 / L0 / T1 / FIX-001 等)"
+    },
+    "title": {
+      "type": "string",
+      "description": "任务标题 (动词+目标，如 'Create unified task schema')"
+    },
+    "description": {
+      "type": "string",
+      "description": "目标+原因 (1-3 句，描述做什么和为什么)"
+    },
+
+    "_comment_CLASSIFICATION": "CLASSIFICATION 区块 (可选) — 任务分类",
+    "type": {
+      "type": "string",
+      "enum": ["infrastructure", "feature", "enhancement", "fix", "refactor", "testing", "docs", "chore"],
+      "description": "任务类型"
+    },
+    "priority": {
+      "type": "string",
+      "enum": ["critical", "high", "medium", "low"],
+      "description": "优先级"
+    },
+    "effort": {
+      "type": "string",
+      "enum": ["small", "medium", "large"],
+      "description": "工作量估算"
+    },
+    "action": {
+      "type": "string",
+      "enum": ["Create", "Update", "Implement", "Refactor", "Add", "Delete", "Configure", "Test", "Fix"],
+      "description": "操作动作 (便于 issue 系统分类)"
+    },
+
+    "_comment_SCOPE": "SCOPE 区块 (可选) — 覆盖范围",
+    "scope": {
+      "oneOf": [
+        { "type": "string" },
+        { "type": "array", "items": { "type": "string" } }
+      ],
+      "description": "覆盖范围 (模块路径或功能区域)"
+    },
+    "excludes": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "明确排除的范围"
+    },
+    "focus_paths": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "重点文件/目录路径"
+    },
+
+    "_comment_DEPENDENCIES": "DEPENDENCIES 区块 (必填) — 依赖关系",
+    "depends_on": {
+      "type": "array",
+      "items": { "type": "string" },
+      "default": [],
+      "description": "依赖任务 ID 列表 (无依赖则 [])"
+    },
+    "parallel_group": {
+      "type": "number",
+      "description": "并行分组编号 (同组可并行执行)"
+    },
+
+    "_comment_CONVERGENCE": "CONVERGENCE 区块 (必填) — 完成标准",
+    "convergence": {
+      "type": "object",
+      "required": ["criteria"],
+      "properties": {
+        "criteria": {
+          "type": "array",
+          "items": { "type": "string" },
+          "minItems": 1,
+          "description": "可测试的完成条件 (可写为断言或手动步骤)"
+        },
+        "verification": {
+          "type": "string",
+          "description": "可执行的验证步骤 (命令或明确步骤)"
+        },
+        "definition_of_done": {
+          "type": "string",
+          "description": "业务语言完成定义 (非技术人员可判断)"
+        }
+      },
+      "additionalProperties": false
+    },
+
+    "_comment_FILES": "FILES 区块 (可选) — 文件级修改点",
+    "files": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["path"],
+        "properties": {
+          "path": {
+            "type": "string",
+            "description": "文件路径"
+          },
+          "action": {
+            "type": "string",
+            "enum": ["modify", "create", "delete"],
+            "description": "文件操作类型"
+          },
+          "target": {
+            "type": "string",
+            "description": "修改目标 (函数名/类名，来自 Solution Schema)"
+          },
+          "changes": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "修改描述列表"
+          },
+          "change": {
+            "type": "string",
+            "description": "单条变更描述 (精确修改说明，合并自 modification_points.change)"
+          },
+          "conflict_risk": {
+            "type": "string",
+            "enum": ["low", "medium", "high"],
+            "description": "冲突风险等级"
+          }
+        },
+        "additionalProperties": false
+      },
+      "description": "涉及文件列表及修改详情"
+    },
+
+    "_comment_IMPLEMENTATION": "IMPLEMENTATION 区块 (可选) — 实施指南",
+    "implementation": {
+      "type": "array",
+      "items": {
+        "oneOf": [
+          { "type": "string" },
+          {
+            "type": "object",
+            "required": ["step", "description"],
+            "properties": {
+              "step": { "type": "string", "description": "步骤编号/名称" },
+              "description": { "type": "string", "description": "步骤描述" },
+              "tdd_phase": { "type": "string", "enum": ["red", "green", "refactor"], "description": "TDD 阶段" },
+              "actions": { "type": "array", "items": { "type": "string" }, "description": "具体操作列表" },
+              "test_fix_cycle": {
+                "type": "object",
+                "properties": {
+                  "max_iterations": { "type": "integer", "default": 3 }
+                },
+                "description": "测试修复循环配置"
+              }
+            },
+            "additionalProperties": false
+          }
+        ]
+      },
+      "description": "步骤化实施指南 — 支持字符串 (简单步骤) 或对象 (含 TDD 阶段等详情)"
+    },
+    "test": {
+      "type": "object",
+      "properties": {
+        "commands": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "测试命令"
+        },
+        "unit": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "单元测试要求"
+        },
+        "integration": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "集成测试要求"
+        },
+        "coverage_target": {
+          "type": "number",
+          "minimum": 0,
+          "maximum": 100,
+          "description": "覆盖率目标 (%)"
+        },
+        "manual_checks": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "手动验证步骤 (合并自 verification_detail)"
+        },
+        "success_metrics": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "量化成功指标 (如 '响应时间 <200ms', '覆盖率 >80%'，合并自 verification_detail)"
+        },
+        "reusable_tools": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "可复用测试工具/脚本"
+        }
+      },
+      "additionalProperties": false,
+      "description": "测试要求"
+    },
+    "regression": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "回归检查点"
+    },
+
+    "_comment_PLANNING": "PLANNING 区块 (可选) — 规划详情 (reference + rationale + risks + code_skeleton)",
+    "reference": {
+      "type": "object",
+      "properties": {
+        "pattern": {
+          "type": "string",
+          "description": "参考模式名称"
+        },
+        "files": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "参考文件路径"
+        },
+        "examples": {
+          "type": "string",
+          "description": "参考指南或示例"
+        }
+      },
+      "additionalProperties": false,
+      "description": "参考实现资料"
+    },
+    "rationale": {
+      "type": "object",
+      "properties": {
+        "chosen_approach": {
+          "type": "string",
+          "description": "选定方案及原因"
+        },
+        "alternatives_considered": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "被考虑但未选择的替代方案"
+        },
+        "decision_factors": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "影响决策的关键因素 (性能、可维护性、成本等)"
+        },
+        "tradeoffs": {
+          "type": "string",
+          "description": "选定方案的已知权衡"
+        }
+      },
+      "additionalProperties": false,
+      "description": "设计决策原因 (Medium/High complexity 时使用)"
+    },
+    "risks": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["description", "probability", "impact", "mitigation"],
+        "properties": {
+          "description": {
+            "type": "string",
+            "description": "风险描述"
+          },
+          "probability": {
+            "type": "string",
+            "enum": ["Low", "Medium", "High"],
+            "description": "发生概率"
+          },
+          "impact": {
+            "type": "string",
+            "enum": ["Low", "Medium", "High"],
+            "description": "影响程度"
+          },
+          "mitigation": {
+            "type": "string",
+            "description": "缓解策略"
+          },
+          "fallback": {
+            "type": "string",
+            "description": "缓解失败时的替代方案"
+          }
+        },
+        "additionalProperties": false
+      },
+      "description": "结构化风险评估"
+    },
+    "code_skeleton": {
+      "type": "object",
+      "properties": {
+        "interfaces": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "name": { "type": "string" },
+              "definition": { "type": "string" },
+              "purpose": { "type": "string" }
+            }
+          },
+          "description": "关键接口/类型定义"
+        },
+        "key_functions": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "signature": { "type": "string" },
+              "purpose": { "type": "string" },
+              "returns": { "type": "string" }
+            }
+          },
+          "description": "关键函数签名"
+        },
+        "classes": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "name": { "type": "string" },
+              "purpose": { "type": "string" },
+              "methods": {
+                "type": "array",
+                "items": { "type": "string" }
+              }
+            }
+          },
+          "description": "关键类结构"
+        }
+      },
+      "additionalProperties": false,
+      "description": "代码骨架 (High complexity 时使用)"
+    },
+
+    "_comment_EXECUTION": "EXECUTION 区块 (可选) — 执行策略",
+    "meta": {
+      "type": "object",
+      "properties": {
+        "agent": {
+          "type": "string",
+          "description": "分配的 agent (@code-developer / @test-fix-agent 等)"
+        },
+        "module": {
+          "type": "string",
+          "description": "所属模块 (frontend/backend/shared)"
+        },
+        "execution_config": {
+          "type": "object",
+          "properties": {
+            "method": {
+              "type": "string",
+              "enum": ["agent", "cli"],
+              "description": "执行方式"
+            },
+            "cli_tool": {
+              "type": "string",
+              "enum": ["codex", "gemini", "qwen", "auto"],
+              "description": "CLI 工具选择"
+            },
+            "enable_resume": {
+              "type": "boolean",
+              "description": "是否启用会话恢复"
+            }
+          },
+          "additionalProperties": false
+        }
+      },
+      "additionalProperties": true,
+      "description": "执行元信息"
+    },
+    "cli_execution": {
+      "type": "object",
+      "properties": {
+        "id": {
+          "type": "string",
+          "description": "CLI 会话 ID (WFS-{session}-TASK-{id})"
+        },
+        "strategy": {
+          "type": "string",
+          "enum": ["new", "resume", "fork", "merge_fork"],
+          "description": "CLI 执行策略"
+        },
+        "resume_from": {
+          "type": "string",
+          "description": "父任务 CLI ID (用于 resume/fork)"
+        },
+        "merge_from": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "合并来源 CLI ID 列表 (用于 merge_fork)"
+        }
+      },
+      "additionalProperties": false,
+      "description": "CLI 执行配置"
+    },
+
+    "_comment_EXTENDED_CONTEXT": "EXTENDED CONTEXT 区块 (可选) — 扩展执行上下文",
+    "pre_analysis": {
+      "type": "array",
+      "description": "Pre-execution analysis steps. Agent executes these before implementation.",
+      "items": {
+        "type": "object",
+        "required": ["step", "action"],
+        "properties": {
+          "step": { "type": "string", "description": "步骤名称" },
+          "action": { "type": "string", "description": "执行动作描述" },
+          "commands": { "type": "array", "items": { "type": "string" }, "description": "执行命令列表" },
+          "command": { "type": "string", "description": "单条执行命令" },
+          "output_to": { "type": "string", "description": "输出存储位置" },
+          "on_error": { "type": "string", "enum": ["fail", "skip_optional", "continue"], "description": "错误处理策略" }
+        },
+        "additionalProperties": false
+      }
+    },
+    "artifacts": {
+      "type": "array",
+      "description": "Brainstorming artifact references for context.",
+      "items": {
+        "type": "object",
+        "properties": {
+          "type": { "type": "string", "description": "产物类型" },
+          "source": { "type": "string", "description": "产物来源" },
+          "path": { "type": "string", "description": "产物路径" },
+          "feature_id": { "type": "string", "description": "关联功能 ID" },
+          "priority": { "type": "string", "description": "优先级" },
+          "usage": { "type": "string", "description": "使用说明" }
+        },
+        "additionalProperties": true
+      }
+    },
+    "inherited": {
+      "type": "object",
+      "description": "Context inherited from parent task.",
+      "properties": {
+        "from": { "type": "string", "description": "父任务 ID" },
+        "context": { "type": "array", "items": { "type": "string" }, "description": "继承的上下文条目" }
+      },
+      "additionalProperties": false
+    },
+
+    "_comment_CONTEXT": "CONTEXT 区块 (可选) — 来源与上下文",
+    "source": {
+      "type": "object",
+      "properties": {
+        "tool": {
+          "type": "string",
+          "description": "产出工具名 (workflow-plan / lite-plan / issue-resolve / review-cycle 等)"
+        },
+        "session_id": {
+          "type": "string",
+          "description": "来源 session ID"
+        },
+        "original_id": {
+          "type": "string",
+          "description": "转换前原始 ID"
+        },
+        "issue_id": {
+          "type": "string",
+          "description": "关联的 Issue ID"
+        }
+      },
+      "additionalProperties": false,
+      "description": "任务来源信息"
+    },
+    "context_package_path": {
+      "type": "string",
+      "description": "上下文包路径"
+    },
+    "evidence": {
+      "type": "array",
+      "description": "支撑证据"
+    },
+    "inputs": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "消费的产物 (文件/资源)"
+    },
+    "outputs": {
+      "type": "array",
+      "items": { "type": "string" },
+      "description": "产出的产物 (文件/资源)"
+    },
+    "commit": {
+      "type": "object",
+      "properties": {
+        "type": {
+          "type": "string",
+          "enum": ["feat", "fix", "refactor", "test", "docs", "chore"],
+          "description": "提交类型"
+        },
+        "scope": {
+          "type": "string",
+          "description": "提交范围"
+        },
+        "message_template": {
+          "type": "string",
+          "description": "提交消息模板"
+        }
+      },
+      "additionalProperties": false,
+      "description": "提交信息模板"
+    },
+
+    "_comment_RUNTIME": "RUNTIME 区块 (执行时填充) — 运行时状态",
+    "status": {
+      "type": "string",
+      "enum": ["pending", "in_progress", "completed", "failed", "skipped", "blocked"],
+      "default": "pending",
+      "description": "执行状态 (执行引擎填充)"
+    },
+    "executed_at": {
+      "type": "string",
+      "format": "date-time",
+      "description": "执行时间戳 (ISO 8601)"
+    },
+    "result": {
+      "type": "object",
+      "properties": {
+        "success": {
+          "type": "boolean",
+          "description": "是否成功"
+        },
+        "files_modified": {
+          "type": "array",
+          "items": { "type": "string" },
+          "description": "修改的文件列表"
+        },
+        "summary": {
+          "type": "string",
+          "description": "执行摘要"
+        },
+        "error": {
+          "type": "string",
+          "description": "错误信息 (失败时)"
+        },
+        "convergence_verified": {
+          "type": "array",
+          "items": { "type": "boolean" },
+          "description": "收敛标准验证结果 (对应 convergence.criteria 每项)"
+        },
+        "commit_hash": {
+          "type": "string",
+          "description": "提交哈希"
+        }
+      },
+      "additionalProperties": false,
+      "description": "执行结果 (执行引擎填充)"
+    }
+  },
+
+  "additionalProperties": true,
+
+  "_field_usage_by_producer": {
+    "workflow-plan": "IDENTITY + CLASSIFICATION + SCOPE + DEPENDENCIES + CONVERGENCE + FILES + IMPLEMENTATION + EXECUTION(pre_analysis + artifacts + inherited + cli_execution + meta) + PLANNING(reference + rationale + risks + code_skeleton) + CONTEXT(context_package_path)",
+    "lite-plan": "IDENTITY + CLASSIFICATION + DEPENDENCIES + CONVERGENCE + FILES",
+    "lite-plan (v2)": "IDENTITY + CLASSIFICATION + SCOPE + DEPENDENCIES + CONVERGENCE + FILES(+change) + IMPLEMENTATION(+manual_checks +success_metrics) + PLANNING(reference + rationale + risks + code_skeleton)",
+    "req-plan": "IDENTITY + CLASSIFICATION + SCOPE + DEPENDENCIES + CONVERGENCE + PLANNING(risks) + CONTEXT(inputs/outputs)",
+    "collaborative-plan": "IDENTITY + CLASSIFICATION + SCOPE + DEPENDENCIES + CONVERGENCE + FILES + CONTEXT(source)",
+    "issue-resolve": "IDENTITY + CLASSIFICATION + SCOPE + DEPENDENCIES + CONVERGENCE + FILES(with target) + IMPLEMENTATION + CONTEXT(commit/source)",
+    "review-cycle": "IDENTITY + CLASSIFICATION + FILES + CONVERGENCE + IMPLEMENTATION + CONTEXT(source/evidence)",
+    "tdd-plan": "IDENTITY + CLASSIFICATION + DEPENDENCIES + CONVERGENCE + EXECUTION + IMPLEMENTATION(test focused)",
+    "analyze-brainstorm": "IDENTITY + CLASSIFICATION + DEPENDENCIES + CONVERGENCE + CONTEXT(evidence/source)"
+  },
+
+  "_directory_convention": {
+    "standard_path": "{session_folder}/.task/",
+    "file_naming": "TASK-{id}.json (或保留原有 ID 前缀: IMPL-, L0-, T1-, FIX-)",
+    "examples": {
+      "workflow-plan": ".workflow/active/WFS-xxx/.task/IMPL-001.json",
+      "lite-plan": ".workflow/.lite-plan/{id}/.task/TASK-001.json",
+      "req-plan": ".workflow/.req-plan/RPLAN-{id}/.task/TASK-001.json",
+      "collab-plan": ".workflow/.planning/CPLAN-{id}/.task/TASK-001.json",
+      "review-cycle": ".workflow/active/WFS-{id}/.review/.task/FIX-001.json",
+      "issue-resolve": ".workflow/issues/{issue-id}/.task/TASK-001.json"
+    }
+  }
+}

.ccw/workflows/cli-templates/schemas/verify-json-schema.json

@@ -0,0 +1,158 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Plan Verification Findings Schema",
+  "description": "Schema for plan verification findings output from cli-explore-agent",
+  "type": "object",
+  "required": [
+    "session_id",
+    "timestamp",
+    "verification_tiers_completed",
+    "findings",
+    "summary"
+  ],
+  "properties": {
+    "session_id": {
+      "type": "string",
+      "description": "Workflow session ID (e.g., WFS-20250127-143000)",
+      "pattern": "^WFS-[0-9]{8}-[0-9]{6}$"
+    },
+    "timestamp": {
+      "type": "string",
+      "description": "ISO 8601 timestamp when verification was completed",
+      "format": "date-time"
+    },
+    "verification_tiers_completed": {
+      "type": "array",
+      "description": "List of verification tiers completed (e.g., ['Tier 1', 'Tier 2'])",
+      "items": {
+        "type": "string",
+        "enum": ["Tier 1", "Tier 2", "Tier 3", "Tier 4"]
+      },
+      "minItems": 1,
+      "maxItems": 4
+    },
+    "findings": {
+      "type": "array",
+      "description": "Array of all findings across all dimensions",
+      "items": {
+        "type": "object",
+        "required": [
+          "id",
+          "dimension",
+          "dimension_name",
+          "severity",
+          "location",
+          "summary",
+          "recommendation"
+        ],
+        "properties": {
+          "id": {
+            "type": "string",
+            "description": "Unique finding ID prefixed by severity (C1, H1, M1, L1)",
+            "pattern": "^[CHML][0-9]+$"
+          },
+          "dimension": {
+            "type": "string",
+            "description": "Verification dimension identifier",
+            "enum": ["A", "B", "C", "D", "E", "F", "G", "H"]
+          },
+          "dimension_name": {
+            "type": "string",
+            "description": "Human-readable dimension name",
+            "enum": [
+              "User Intent Alignment",
+              "Requirements Coverage Analysis",
+              "Consistency Validation",
+              "Dependency Integrity",
+              "Synthesis Alignment",
+              "Task Specification Quality",
+              "Duplication Detection",
+              "Feasibility Assessment"
+            ]
+          },
+          "severity": {
+            "type": "string",
+            "description": "Severity level of the finding",
+            "enum": ["CRITICAL", "HIGH", "MEDIUM", "LOW"]
+          },
+          "location": {
+            "type": "array",
+            "description": "Array of locations where issue was found (e.g., 'IMPL_PLAN.md:L45', 'task:IMPL-1.2', 'synthesis:FR-03')",
+            "items": {
+              "type": "string"
+            },
+            "minItems": 1
+          },
+          "summary": {
+            "type": "string",
+            "description": "Concise summary of the issue (1-2 sentences)",
+            "minLength": 10,
+            "maxLength": 500
+          },
+          "recommendation": {
+            "type": "string",
+            "description": "Actionable recommendation to resolve the issue",
+            "minLength": 10,
+            "maxLength": 500
+          }
+        }
+      }
+    },
+    "summary": {
+      "type": "object",
+      "description": "Aggregate summary of verification results",
+      "required": [
+        "critical_count",
+        "high_count",
+        "medium_count",
+        "low_count",
+        "total_findings",
+        "coverage_percentage",
+        "recommendation"
+      ],
+      "properties": {
+        "critical_count": {
+          "type": "integer",
+          "description": "Number of critical severity findings",
+          "minimum": 0
+        },
+        "high_count": {
+          "type": "integer",
+          "description": "Number of high severity findings",
+          "minimum": 0
+        },
+        "medium_count": {
+          "type": "integer",
+          "description": "Number of medium severity findings",
+          "minimum": 0
+        },
+        "low_count": {
+          "type": "integer",
+          "description": "Number of low severity findings",
+          "minimum": 0
+        },
+        "total_findings": {
+          "type": "integer",
+          "description": "Total number of findings",
+          "minimum": 0
+        },
+        "coverage_percentage": {
+          "type": "number",
+          "description": "Percentage of synthesis requirements covered by tasks (0-100)",
+          "minimum": 0,
+          "maximum": 100
+        },
+        "recommendation": {
+          "type": "string",
+          "description": "Quality gate recommendation",
+          "enum": [
+            "BLOCK_EXECUTION",
+            "PROCEED_WITH_FIXES",
+            "PROCEED_WITH_CAUTION",
+            "PROCEED"
+          ]
+        }
+      }
+    }
+  }
+}