claude-code-workflow 7.2.24 → 7.2.26

package/.claude/skills/review-cycle/SKILL.md

@@ -1,132 +1,132 @@
----
-name: review-cycle
-description: Unified multi-dimensional code review with automated fix orchestration. Routes to session-based (git changes), module-based (path patterns), or fix mode. Triggers on "workflow:review-cycle", "workflow:review-session-cycle", "workflow:review-module-cycle", "workflow:review-cycle-fix".
-allowed-tools: Agent, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, Read, Write, Edit, Bash, Glob, Grep, Skill
----
-
-# Review Cycle
-
-Unified code review orchestrator with mode-based routing. Detects input type and dispatches to the appropriate execution phase.
-
-## Architecture Overview
-
-```
-┌──────────────────────────────────────────────────────────┐
-│  Review Cycle Orchestrator (SKILL.md)                     │
-│  → Parse input → Detect mode → Read phase doc → Execute   │
-└───────────────────────────┬──────────────────────────────┘
-                            │
-          ┌─────────────────┼─────────────────┐
-          ↓                 ↓                 ↓
-   ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
-   │   session    │  │   module    │  │    fix      │
-   │  (git changes│  │(path pattern│  │(export file │
-   │   review)    │  │   review)   │  │  auto-fix)  │
-   └─────────────┘  └─────────────┘  └─────────────┘
-   phases/           phases/           phases/
-   review-session.md review-module.md  review-fix.md
-```
-
-## Auto Mode Detection
-
-```javascript
-// ★ 统一 auto mode 检测：-y/--yes 从 $ARGUMENTS 或 ccw 传播
-const autoYes = /\b(-y|--yes)\b/.test($ARGUMENTS)
-```
-
-When `autoYes` is true, skip all interactive confirmations and use defaults throughout the review cycle phases.
-
-## Mode Detection
-
-```javascript
-function detectMode(args) {
-  if (args.includes('--fix')) return 'fix';
-  if (args.match(/\*|\.ts|\.js|\.py|\.vue|\.jsx|\.tsx|src\/|lib\//)) return 'module';
-  if (args.match(/^WFS-/) || args.trim() === '') return 'session';
-  return 'session';  // default
-}
-```
-
-| Input Pattern | Detected Mode | Phase Doc |
-|---------------|---------------|-----------|
-| `src/auth/**` | `module` | phases/review-module.md |
-| `src/auth/**,src/payment/**` | `module` | phases/review-module.md |
-| `WFS-payment-integration` | `session` | phases/review-session.md |
-| _(empty)_ | `session` | phases/review-session.md |
-| `--fix .review/` | `fix` | phases/review-fix.md |
-| `--fix --resume` | `fix` | phases/review-fix.md |
-
-## Usage
-
-```
-Skill(skill="review-cycle", args="src/auth/**")                                    # Module mode
-Skill(skill="review-cycle", args="src/auth/** --dimensions=security,architecture") # Module + custom dims
-Skill(skill="review-cycle", args="WFS-payment-integration")                        # Session mode
-Skill(skill="review-cycle", args="")                                               # Session: auto-detect
-Skill(skill="review-cycle", args="--fix .workflow/active/WFS-123/.review/")        # Fix mode
-Skill(skill="review-cycle", args="--fix --resume")                                 # Fix: resume
-Skill(skill="review-cycle", args="-y src/auth/**")                                 # Auto mode (skip confirmations)
-
-# Common flags (all modes):
---dimensions=dim1,dim2,...    Custom dimensions (default: all 7)
---max-iterations=N           Max deep-dive iterations (default: 3)
-
-# Fix-only flags:
---fix                        Enter fix pipeline
---resume                     Resume interrupted fix session
---batch-size=N               Findings per planning batch (default: 5)
---max-iterations=N           Max retry per finding (default: 3)
-```
-
-## Execution Flow
-
-```
-1. Parse $ARGUMENTS → extract mode + flags
-2. Detect mode (session | module | fix)
-3. Read corresponding phase doc:
-   - session → Read phases/review-session.md → execute
-   - module  → Read phases/review-module.md  → execute
-   - fix     → Read phases/review-fix.md     → execute
-4. Phase doc contains full execution detail (5 phases for review, 4+1 phases for fix)
-```
-
-**Phase Reference Documents** (read on-demand based on detected mode):
-
-| Mode | Document | Source | Description |
-|------|----------|--------|-------------|
-| session | [phases/review-session.md](phases/review-session.md) | review-session-cycle.md | Session-based review: git changes → 7-dimension parallel analysis → aggregation → deep-dive → completion |
-| module | [phases/review-module.md](phases/review-module.md) | review-module-cycle.md | Module-based review: path patterns → 7-dimension parallel analysis → aggregation → deep-dive → completion |
-| fix | [phases/review-fix.md](phases/review-fix.md) | review-cycle-fix.md | Automated fix: export file → intelligent batching → parallel planning → execution → completion |
-
-## Project Context
-
-Run `ccw spec load --category review` for review standards, checklists, and approval gates.
-
-## Core Rules
-
-1. **Mode Detection First**: Parse input to determine session/module/fix mode before anything else
-2. **Progressive Loading**: Read ONLY the phase doc for the detected mode, not all three
-3. **Full Delegation**: Once mode is detected, the phase doc owns the entire execution flow
-4. **Auto-Continue**: Phase docs contain their own multi-phase execution (Phase 1-5 or Phase 1-4+5)
-5. **DO NOT STOP**: Continuous execution until all internal phases within the phase doc complete
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Cannot determine mode from input | AskUserQuestion to clarify intent |
-| Phase doc not found | Error and exit with file path |
-| Invalid flags for mode | Warn and continue with defaults |
-
-## Related Commands
-
-```bash
-# View review/fix progress dashboard
-ccw view
-
-# Workflow pipeline
-# Step 1: Review
-Skill(skill="review-cycle", args="src/auth/**")
-# Step 2: Fix (after review complete)
-Skill(skill="review-cycle", args="--fix .workflow/active/WFS-{session-id}/.review/")
-```
+---
+name: review-cycle
+description: "Unified multi-dimensional code review with automated fix orchestration. Routes to session-based (git changes), module-based (path patterns), or fix mode. Triggers on \"workflow:review-cycle\", \"workflow:review-session-cycle\", \"workflow:review-module-cycle\", \"workflow:review-cycle-fix\"."
+allowed-tools: Agent, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, Read, Write, Edit, Bash, Glob, Grep, Skill
+---
+
+# Review Cycle
+
+Unified code review orchestrator with mode-based routing. Detects input type and dispatches to the appropriate execution phase.
+
+## Architecture Overview
+
+```
+┌──────────────────────────────────────────────────────────┐
+│  Review Cycle Orchestrator (SKILL.md)                     │
+│  → Parse input → Detect mode → Read phase doc → Execute   │
+└───────────────────────────┬──────────────────────────────┘
+                            │
+          ┌─────────────────┼─────────────────┐
+          ↓                 ↓                 ↓
+   ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
+   │   session    │  │   module    │  │    fix      │
+   │  (git changes│  │(path pattern│  │(export file │
+   │   review)    │  │   review)   │  │  auto-fix)  │
+   └─────────────┘  └─────────────┘  └─────────────┘
+   phases/           phases/           phases/
+   review-session.md review-module.md  review-fix.md
+```
+
+## Auto Mode Detection
+
+```javascript
+// ★ 统一 auto mode 检测：-y/--yes 从 $ARGUMENTS 或 ccw 传播
+const autoYes = /\b(-y|--yes)\b/.test($ARGUMENTS)
+```
+
+When `autoYes` is true, skip all interactive confirmations and use defaults throughout the review cycle phases.
+
+## Mode Detection
+
+```javascript
+function detectMode(args) {
+  if (args.includes('--fix')) return 'fix';
+  if (args.match(/\*|\.ts|\.js|\.py|\.vue|\.jsx|\.tsx|src\/|lib\//)) return 'module';
+  if (args.match(/^WFS-/) || args.trim() === '') return 'session';
+  return 'session';  // default
+}
+```
+
+| Input Pattern | Detected Mode | Phase Doc |
+|---------------|---------------|-----------|
+| `src/auth/**` | `module` | phases/review-module.md |
+| `src/auth/**,src/payment/**` | `module` | phases/review-module.md |
+| `WFS-payment-integration` | `session` | phases/review-session.md |
+| _(empty)_ | `session` | phases/review-session.md |
+| `--fix .review/` | `fix` | phases/review-fix.md |
+| `--fix --resume` | `fix` | phases/review-fix.md |
+
+## Usage
+
+```
+Skill(skill="review-cycle", args="src/auth/**")                                    # Module mode
+Skill(skill="review-cycle", args="src/auth/** --dimensions=security,architecture") # Module + custom dims
+Skill(skill="review-cycle", args="WFS-payment-integration")                        # Session mode
+Skill(skill="review-cycle", args="")                                               # Session: auto-detect
+Skill(skill="review-cycle", args="--fix .workflow/active/WFS-123/.review/")        # Fix mode
+Skill(skill="review-cycle", args="--fix --resume")                                 # Fix: resume
+Skill(skill="review-cycle", args="-y src/auth/**")                                 # Auto mode (skip confirmations)
+
+# Common flags (all modes):
+--dimensions=dim1,dim2,...    Custom dimensions (default: all 7)
+--max-iterations=N           Max deep-dive iterations (default: 3)
+
+# Fix-only flags:
+--fix                        Enter fix pipeline
+--resume                     Resume interrupted fix session
+--batch-size=N               Findings per planning batch (default: 5)
+--max-iterations=N           Max retry per finding (default: 3)
+```
+
+## Execution Flow
+
+```
+1. Parse $ARGUMENTS → extract mode + flags
+2. Detect mode (session | module | fix)
+3. Read corresponding phase doc:
+   - session → Read phases/review-session.md → execute
+   - module  → Read phases/review-module.md  → execute
+   - fix     → Read phases/review-fix.md     → execute
+4. Phase doc contains full execution detail (5 phases for review, 4+1 phases for fix)
+```
+
+**Phase Reference Documents** (read on-demand based on detected mode):
+
+| Mode | Document | Source | Description |
+|------|----------|--------|-------------|
+| session | [phases/review-session.md](phases/review-session.md) | review-session-cycle.md | Session-based review: git changes → 7-dimension parallel analysis → aggregation → deep-dive → completion |
+| module | [phases/review-module.md](phases/review-module.md) | review-module-cycle.md | Module-based review: path patterns → 7-dimension parallel analysis → aggregation → deep-dive → completion |
+| fix | [phases/review-fix.md](phases/review-fix.md) | review-cycle-fix.md | Automated fix: export file → intelligent batching → parallel planning → execution → completion |
+
+## Project Context
+
+Run `ccw spec load --category review` for review standards, checklists, and approval gates.
+
+## Core Rules
+
+1. **Mode Detection First**: Parse input to determine session/module/fix mode before anything else
+2. **Progressive Loading**: Read ONLY the phase doc for the detected mode, not all three
+3. **Full Delegation**: Once mode is detected, the phase doc owns the entire execution flow
+4. **Auto-Continue**: Phase docs contain their own multi-phase execution (Phase 1-5 or Phase 1-4+5)
+5. **DO NOT STOP**: Continuous execution until all internal phases within the phase doc complete
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| Cannot determine mode from input | AskUserQuestion to clarify intent |
+| Phase doc not found | Error and exit with file path |
+| Invalid flags for mode | Warn and continue with defaults |
+
+## Related Commands
+
+```bash
+# View review/fix progress dashboard
+ccw view
+
+# Workflow pipeline
+# Step 1: Review
+Skill(skill="review-cycle", args="src/auth/**")
+# Step 2: Fix (after review complete)
+Skill(skill="review-cycle", args="--fix .workflow/active/WFS-{session-id}/.review/")
+```

package/.claude/skills/review-cycle/phases/review-module.md

@@ -401,7 +401,7 @@ Task(
     1. Read review state: ${reviewStateJsonPath}
     2. Get target files: Read resolved_files from review-state.json
     3. Validate file access: bash(ls -la ${targetFiles.join(' ')})
-    4. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
+    4. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"review-dim"}' (get output schema summary)
     5. Read: .workflow/project-tech.json (technology stack and architecture context)
     6. Read: .workflow/specs/*.md (user-defined constraints and conventions to validate against)
 
@@ -456,7 +456,7 @@ Task(
     ${getDimensionGuidance(dimension)}
 
     ## Success Criteria
-    - [ ] Schema obtained via cat review-dimension-results-schema.json
+    - [ ] Schema obtained via json_builder info
     - [ ] All target files analyzed for ${dimension} concerns
     - [ ] All findings include file:line references with code snippets
     - [ ] Severity assessment follows established criteria (see reference)
@@ -505,7 +505,7 @@ Task(
     2. Read affected file: ${file}
     3. Identify related code: bash(grep -r "import.*${basename(file)}" ${projectDir}/src --include="*.ts")
     4. Read test files: bash(find ${projectDir}/tests -name "*${basename(file, '.ts')}*" -type f)
-    5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-deep-dive-results-schema.json (get output schema reference)
+    5. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"review-deep"}' (get output schema summary)
     6. Read: .workflow/project-tech.json (technology stack and architecture context)
     7. Read: .workflow/specs/*.md (user-defined constraints for remediation compliance)
 
@@ -538,7 +538,7 @@ Task(
        - Impact assessment and rollback strategy
 
     ## Success Criteria
-    - [ ] Schema obtained via cat review-deep-dive-results-schema.json
+    - [ ] Schema obtained via json_builder info
     - [ ] Root cause clearly identified with supporting evidence
     - [ ] Remediation plan is step-by-step actionable with exact file:line references
     - [ ] Each step includes specific commands and validation tests

package/.claude/skills/review-cycle/phases/review-session.md

@@ -412,7 +412,7 @@ Task(
     2. Read completed task summaries: bash(find ${summariesDir} -name "IMPL-*.md" -type f)
     3. Get changed files: bash(cd ${workflowDir} && git log --since="${sessionCreatedAt}" --name-only --pretty=format: | sort -u)
     4. Read review state: ${reviewStateJsonPath}
-    5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
+    5. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"review-dim"}' (get output schema summary)
     6. Read: .workflow/project-tech.json (technology stack and architecture context)
     7. Read: .workflow/specs/*.md (user-defined constraints and conventions to validate against)
 
@@ -467,7 +467,7 @@ Task(
     ${getDimensionGuidance(dimension)}
 
     ## Success Criteria
-    - [ ] Schema obtained via cat review-dimension-results-schema.json
+    - [ ] Schema obtained via json_builder info
     - [ ] All changed files analyzed for ${dimension} concerns
     - [ ] All findings include file:line references with code snippets
     - [ ] Severity assessment follows established criteria (see reference)
@@ -516,7 +516,7 @@ Task(
     2. Read affected file: ${file}
     3. Identify related code: bash(grep -r "import.*${basename(file)}" ${workflowDir}/src --include="*.ts")
     4. Read test files: bash(find ${workflowDir}/tests -name "*${basename(file, '.ts')}*" -type f)
-    5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-deep-dive-results-schema.json (get output schema reference)
+    5. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"review-deep"}' (get output schema summary)
     6. Read: .workflow/project-tech.json (technology stack and architecture context)
     7. Read: .workflow/specs/*.md (user-defined constraints for remediation compliance)
 
@@ -550,7 +550,7 @@ Task(
        - Impact assessment and rollback strategy
 
     ## Success Criteria
-    - [ ] Schema obtained via cat review-deep-dive-results-schema.json
+    - [ ] Schema obtained via json_builder info
     - [ ] Root cause clearly identified with supporting evidence
     - [ ] Remediation plan is step-by-step actionable with exact file:line references
     - [ ] Each step includes specific commands and validation tests

package/.claude/skills/spec-generator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spec-generator
-description: Specification generator - 6 phase document chain producing product brief, PRD, architecture, and epics. Triggers on "generate spec", "create specification", "spec generator", "workflow:spec".
+description: "Specification generator - 7 phase document chain producing product brief, PRD, architecture, epics, and issues with Codex review gates. Triggers on generate spec, create specification, spec generator, workflow:spec."
 allowed-tools: Agent, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, Read, Write, Edit, Bash, Glob, Grep, Skill
 ---
 

package/.claude/skills/team-designer/phases/02-scaffold-generation.md

@@ -37,7 +37,7 @@ The SKILL.md follows a strict template. Every generated SKILL.md contains these
 ```yaml
 ---
 name: ${teamConfig.skillName}
-description: ${teamConfig.domain}. Triggers on "${teamConfig.skillName}".
+description: "${teamConfig.domain}. Triggers on ${teamConfig.skillName}."
 allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*)
 ---
 ```

package/.claude/skills/team-lifecycle-v4/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: team-lifecycle-v4
-description: Full lifecycle team skill with clean architecture. SKILL.md is a universal router — all roles read it. Beat model is coordinator-only. Structure is roles/ + specs/ + templates/. Triggers on "team lifecycle v4".
+description: Full lifecycle team skill — plan, develop, test, review in one coordinated session. Role-based architecture with coordinator-driven beat model. Triggers on "team lifecycle v4".
 allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*)
 ---
 

package/.claude/skills/team-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: team-review
-description: Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on "team-review".
+description: "Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review."
 allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*)
 ---
 

package/.claude/skills/team-ultra-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: team-ultra-analyze
-description: Deep collaborative analysis team skill. All roles route via this SKILL.md. Beat model is coordinator-only (monitor.md). Structure is roles/ + specs/. Triggers on "team ultra-analyze", "team analyze".
+description: Deep collaborative analysis team skill. Multi-role investigation with coordinator-driven synthesis. Triggers on "team ultra-analyze", "team analyze".
 allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*)
 ---
 

package/.claude/skills/workflow-multi-cli-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-multi-cli-plan
-description: Multi-CLI collaborative planning with ACE context gathering, iterative cross-verification, and execution handoff
+description: Multi-CLI collaborative planning with codebase context gathering, iterative cross-verification, and execution handoff.
 allowed-tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep
 ---
 
@@ -246,8 +246,8 @@ Agent({
   description: "Generate implementation plan",
   prompt: `
 ## Schema Reference
-Execute: cat ~/.ccw/workflows/cli-templates/schemas/plan-overview-base-schema.json
-Execute: cat ~/.ccw/workflows/cli-templates/schemas/task-schema.json
+Execute: ccw tool exec json_builder '{"cmd":"info","schema":"plan"}'
+Execute: ccw tool exec json_builder '{"cmd":"info","schema":"task"}'
 
 ## Output Format: Two-Layer Structure
 - plan.json: Overview with task_ids[] referencing .task/ files (NO tasks[] array)

package/.claude/skills/workflow-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-plan
-description: Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning. Triggers on "workflow-plan", "workflow-plan-verify", "workflow:replan".
+description: "Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning. Triggers on \"workflow-plan\", \"workflow-plan-verify\", \"workflow:replan\"."
 allowed-tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/.claude/skills/workflow-plan/phases/03-conflict-resolution.md

@@ -70,7 +70,7 @@ Task(subagent_type="cli-execution-agent", run_in_background=false, prompt=`
   ## Analysis Steps
 
   ### 0. Load Output Schema (MANDATORY)
-  Execute: cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json
+  Execute: ccw tool exec json_builder '{"cmd":"info","schema":"conflict"}' (get schema summary)
 
   ### 1. Load Context
   - Read existing files from conflict_detection.existing_files
@@ -119,7 +119,7 @@ Task(subagent_type="cli-execution-agent", run_in_background=false, prompt=`
 
   Output to conflict-resolution.json (generated in Phase 4)
 
-  **Schema Reference**: Execute cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json to get full schema
+  **Schema Reference**: Execute ccw tool exec json_builder '{"cmd":"info","schema":"conflict"}' to get schema summary
 
   Return JSON following the schema. Key requirements:
   - Minimum 2 strategies per conflict, max 4

package/.claude/skills/workflow-plan/phases/05-plan-verify.md

@@ -195,8 +195,8 @@ Task(
 ## Plan Verification Task
 
 ### MANDATORY FIRST STEPS
-1. Read: ~/.ccw/workflows/cli-templates/schemas/plan-verify-agent-schema.json (dimensions & rules)
-2. Read: ~/.ccw/workflows/cli-templates/schemas/verify-json-schema.json (output schema)
+1. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"plan-verify"}' (dimensions & rules)
+2. Execute: ccw tool exec json_builder '{"cmd":"info","schema":"verify"}' (output schema)
 3. Read: ${session_file} (user intent)
 4. Read: ${PLANNING_NOTES} (constraints & N+1 context)
 5. Read: ${IMPL_PLAN} (implementation plan)

package/.claude/skills/workflow-tdd-plan/phases/02-context-gathering.md

@@ -99,7 +99,7 @@ Execute **${angle}** exploration for TDD task planning context. Analyze codebase
 ## MANDATORY FIRST STEPS (Execute by Agent)
 1. Run: ccw tool exec get_modules_by_depth '{}' (project structure)
 2. Run: rg -l "{keyword_from_task}" --type ts (locate relevant files)
-3. Execute: cat ~/.ccw/workflows/cli-templates/schemas/explore-json-schema.json (get output schema reference)
+3. Execute: ccw tool exec json_builder '{"cmd":"init","schema":"explore","output":"${sessionFolder}/exploration-${angle}.json"}' (init output + get schema info)
 
 ## Exploration Strategy (${angle} focus)
 
@@ -121,7 +121,7 @@ Execute **${angle}** exploration for TDD task planning context. Analyze codebase
 
 **File**: ${sessionFolder}/exploration-${angle}.json
 
-**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 3, follow schema exactly
+**Schema Reference**: Skeleton initialized via json_builder in step 3. Use `set` to populate fields, `validate` before returning.
 
 **Required Fields** (all ${angle} focused):
 - project_structure: Modules/architecture relevant to ${angle}
@@ -141,7 +141,7 @@ Execute **${angle}** exploration for TDD task planning context. Analyze codebase
 - _metadata.exploration_angle: "${angle}"
 
 ## Success Criteria
-- [ ] Schema obtained via cat explore-json-schema.json
+- [ ] Schema initialized via json_builder init
 - [ ] get_modules_by_depth.sh executed
 - [ ] At least 3 relevant files identified with ${angle} rationale
 - [ ] Patterns are actionable (code examples, not generic advice)

package/.claude/skills/workflow-tdd-plan/phases/04-conflict-resolution.md

@@ -70,7 +70,7 @@ Task(subagent_type="cli-execution-agent", run_in_background=false, prompt=`
   ## Analysis Steps
 
   ### 0. Load Output Schema (MANDATORY)
-  Execute: cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json
+  Execute: ccw tool exec json_builder '{"cmd":"info","schema":"conflict"}'
 
   ### 1. Load Context
   - Read existing files from conflict_detection.existing_files
@@ -119,7 +119,7 @@ Task(subagent_type="cli-execution-agent", run_in_background=false, prompt=`
 
   Output to conflict-resolution.json (generated in Phase 4)
 
-  **Schema Reference**: Execute cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json to get full schema
+  **Schema Reference**: Execute ccw tool exec json_builder '{"cmd":"info","schema":"conflict"}' to get schema summary
 
   Return JSON following the schema. Key requirements:
   - Minimum 2 strategies per conflict, max 4

package/.claude/skills/workflow-test-fix/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-test-fix
-description: Unified test-fix pipeline combining test generation (session, context, analysis, task gen) with iterative test-cycle execution (adaptive strategy, progressive testing, CLI fallback). Triggers on "workflow-test-fix", "workflow-test-fix", "test fix workflow".
+description: Unified test-fix pipeline combining test generation (session, context, analysis, task gen) with iterative test-cycle execution (adaptive strategy, progressive testing, CLI fallback). Triggers on "workflow-test-fix", "test fix workflow".
 allowed-tools: Skill, Agent, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/.claude/skills/workflow-test-fix/phases/02-test-context-gather.md

@@ -223,7 +223,7 @@ Execute **${angle}** exploration for task planning context. Analyze codebase fro
 ## MANDATORY FIRST STEPS (Execute by Agent)
 1. Run: ccw tool exec get_modules_by_depth '{}' (project structure)
 2. Run: rg -l "{keyword_from_task}" --type ts (locate relevant files)
-3. Execute: cat ~/.ccw/workflows/cli-templates/schemas/explore-json-schema.json (get output schema reference)
+3. Execute: ccw tool exec json_builder '{"cmd":"init","schema":"explore","output":"${sessionFolder}/exploration-${angle}.json"}' (init output + get schema info)
 
 ## Exploration Strategy (${angle} focus)
 
@@ -265,7 +265,7 @@ Execute **${angle}** exploration for task planning context. Analyze codebase fro
 - _metadata.exploration_angle: "${angle}"
 
 ## Success Criteria
-- [ ] Schema obtained via cat explore-json-schema.json
+- [ ] Schema initialized via json_builder init
 - [ ] get_modules_by_depth.sh executed
 - [ ] At least 3 relevant files identified with ${angle} rationale
 - [ ] Patterns are actionable (code examples, not generic advice)

package/.codex/AGENTS.md

@@ -105,6 +105,22 @@ ACE search_context (semantic) → smart_search (structured) → read_file (batch
 
 **NEVER** use shell commands (`cat`, `find`, `grep`) when MCP tools are available.
 
+## Workflow Session Awareness
+
+| Workflow | Directory | Summary File |
+|----------|-----------|-------------|
+| `workflow-plan` | `.workflow/active/WFS-*/` | `workflow-session.json` |
+| `workflow-lite-plan` | `.workflow/.lite-plan/{slug}-{date}/` | `plan.json` |
+| `analyze-with-file` | `.workflow/.analysis/ANL-*/` | `conclusions.json` |
+| `multi-cli-plan` | `.workflow/.multi-cli-plan/*/` | `session-state.json` |
+| `lite-fix` | `.workflow/.lite-fix/*/` | `fix-plan.json` |
+| Other | `.workflow/.debug/`, `.workflow/.scratchpad/`, `.workflow/archives/` | — |
+
+Before starting work, scan recent sessions (7 days) to avoid conflicts and reuse prior work:
+- Overlapping file scope → warn, suggest referencing prior session
+- Complementary findings → feed into current task context
+
+
 ## Execution Checklist
 
 **Before**: