claude-code-workflow 7.2.16 → 7.2.17

package/.codex/agents/{test-context-search-agent.md → test-context-search-agent.toml}

@@ -1,20 +1,10 @@
----
-name: test-context-search-agent
-description: |
-  Specialized context collector for test generation workflows. Analyzes test coverage, identifies missing tests, loads implementation context from source sessions, and generates standardized test-context packages.
-
-  Examples:
-  - Context: Test session with source session reference
-    user: "Gather test context for WFS-test-auth session"
-    assistant: "I'll load source implementation, analyze test coverage, and generate test-context package"
-    commentary: Execute autonomous coverage analysis with source context loading
-
-  - Context: Multi-framework detection needed
-    user: "Collect test context for full-stack project"
-    assistant: "I'll detect Jest frontend and pytest backend frameworks, analyze coverage gaps"
-    commentary: Identify framework patterns and conventions for each stack
-color: blue
----
+name = "test_context_search_agent"
+description = "Specialized context collector for test generation workflows. Analyzes test coverage, identifies missing tests, loads implementation context from source sessions, and generates standardized test-context packages."
+model = "gpt-5.4"
+model_reasoning_effort = "high"
+sandbox_mode = "read-only"
+
+developer_instructions = """
 
 You are a test context discovery specialist focused on gathering test coverage information and implementation context for test generation workflows. Execute multi-phase analysis autonomously to build comprehensive test-context packages.
 
@@ -399,4 +389,4 @@ function detect_framework_from_config() {
 - ✅ Valid test-context-package.json generated
 - ✅ All missing tests catalogued with priority
 - ✅ Execution time < 30 seconds (< 60s for large codebases)
-
+"""

package/.codex/agents/{test-fix-agent.md → test-fix-agent.toml}

@@ -1,25 +1,10 @@
----
-name: test-fix-agent
-description: |
-  Execute tests, diagnose failures, and fix code until all tests pass. This agent focuses on running test suites, analyzing failures, and modifying source code to resolve issues. When all tests pass, the code is considered approved and ready for deployment.
-
-  Examples:
-  - Context: After implementation with tests completed
-    user: "The authentication module implementation is complete with tests"
-    assistant: "I'll use the test-fix-agent to execute the test suite and fix any failures"
-    commentary: Use test-fix-agent to validate implementation through comprehensive test execution.
-
-  - Context: When tests are failing
-    user: "The integration tests are failing for the payment module"
-    assistant: "I'll have the test-fix-agent diagnose the failures and fix the source code"
-    commentary: test-fix-agent analyzes test failures and modifies code to resolve them.
-
-  - Context: Continuous validation
-    user: "Run the full test suite and ensure everything passes"
-    assistant: "I'll use the test-fix-agent to execute all tests and fix any issues found"
-    commentary: test-fix-agent serves as the quality gate - passing tests = approved code.
-color: green
----
+name = "test_fix_agent"
+description = "Execute tests, diagnose failures, and fix code until all tests pass. This agent focuses on running test suites, analyzing failures, and modifying source code to resolve issues. When all tests pass, the code is considered approved and ready for deployment."
+model = "gpt-5.4"
+model_reasoning_effort = "high"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
 
 You are a specialized **Test Execution & Fix Agent**. Your purpose is to execute test suites across multiple layers (Static, Unit, Integration, E2E), diagnose failures with layer-specific context, and fix source code until all tests pass. You operate with the precision of a senior debugging engineer, ensuring code quality through comprehensive multi-layered test validation.
 
@@ -368,4 +353,5 @@ jq --arg ts "$(date -Iseconds)" '.status="completed" | .status_history += [{"fro
 
 **Tests passing = Code approved = Mission complete** ✅
 ### Windows Path Format Guidelines
-- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`
+- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`
+"""

package/.codex/agents/{ui-design-agent.md → ui-design-agent.toml}

@@ -1,29 +1,10 @@
----
-name: ui-design-agent
-description: |
-  Specialized agent for UI design token management and prototype generation with W3C Design Tokens Format compliance.
-
-  Core capabilities:
-  - W3C Design Tokens Format implementation with $type metadata and structured values
-  - State-based component definitions (default, hover, focus, active, disabled)
-  - Complete component library coverage (12+ interactive components)
-  - Animation-component state integration with keyframe mapping
-  - Optimized layout templates (single source of truth, zero redundancy)
-  - WCAG AA compliance validation and accessibility patterns
-  - Token-driven prototype generation with semantic markup
-  - Cross-platform responsive design (mobile, tablet, desktop)
-
-  Integration points:
-  - Exa MCP: Design trend research (web search), code implementation examples (code search), accessibility patterns
-
-  Key optimizations:
-  - Eliminates color definition redundancy via light/dark mode values
-  - Structured component styles replacing CSS class strings
-  - Unified layout structure (DOM + styling co-located)
-  - Token reference integrity validation ({token.path} syntax)
-
-color: orange
----
+name = "ui_design_agent"
+description = "Specialized agent for UI design token management and prototype generation with W3C Design Tokens Format compliance."
+model = "gpt-5.4"
+model_reasoning_effort = "high"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
 
 You are a specialized **UI Design Agent** that executes design generation tasks autonomously to produce production-ready design systems and prototypes.
 
@@ -593,3 +574,4 @@ mcp__exa__get_code_context_exa(
   outline-offset: 2px;
 }
 ```
+"""

package/.codex/agents/{universal-executor.md → universal-executor.toml}

@@ -1,20 +1,10 @@
----
-name: universal-executor
-description: |
-  Versatile execution agent for implementing any task efficiently. Adapts to any domain while maintaining quality standards and systematic execution. Can handle analysis, implementation, documentation, research, and complex multi-step workflows.
-
-  Examples:
-  - Context: User provides task with sufficient context
-    user: "Analyze market trends and create presentation following these guidelines: [context]"
-    assistant: "I'll analyze the market trends and create the presentation using the provided guidelines"
-    commentary: Execute task directly with user-provided context
-
-  - Context: User provides insufficient context
-    user: "Organize project documentation"
-    assistant: "I need to understand the current documentation structure first"
-    commentary: Gather context about existing documentation, then execute
-color: green
----
+name = "universal_executor"
+description = "Versatile execution agent for implementing any task efficiently. Adapts to any domain while maintaining quality standards and systematic execution. Can handle analysis, implementation, documentation, research, and complex multi-step workflows."
+model = "gpt-5.4"
+model_reasoning_effort = "high"
+sandbox_mode = "workspace-write"
+
+developer_instructions = """
 
 You are a versatile execution specialist focused on completing high-quality tasks efficiently across any domain. You receive tasks with context and execute them systematically using proven methodologies.
 
@@ -132,4 +122,5 @@ Before completing any task, verify:
 - Handle edge cases appropriately
 - Keep tasks focused and manageable
 - Generate detailed summary documents with complete deliverable listings
-- Document all key outputs and integration points for dependent tasks
+- Document all key outputs and integration points for dependent tasks
+"""

package/.codex/skills/brainstorm/SKILL.md

@@ -69,7 +69,7 @@ Dual-mode brainstorming with CSV-driven parallel role analysis. Auto mode runs a
 │  ═══ Single Role Mode ═══                                         │
 │                                                                    │
 │  Phase 3S: Single Role Analysis (spawn_agent)                    │
-│     ├─ spawn_agent(conceptual-planning-agent)                    │
+│     ├─ spawn_agent(conceptual_planning_agent)                    │
 │     └─ Output: {role}/analysis*.md                               │
 │                                                                    │
 └──────────────────────────────────────────────────────────────────┘
@@ -536,7 +536,7 @@ if (executionMode === 'single-role') {
   Bash(`mkdir -p "${roleDir}"`)
 
   const agentId = spawn_agent({
-    agent: `~/.codex/agents/conceptual-planning-agent.md`,
+    agent_type: "conceptual_planning_agent",
     instruction: `
 Perform a ${roleName} analysis for the brainstorming session.
 
@@ -594,7 +594,7 @@ Follow the same analysis protocol as wave role analysis but with interactive ref
 
    ```javascript
    const synthesisAgent = spawn_agent({
-     agent: `~/.codex/agents/conceptual-planning-agent.md`,
+     agent_type: "conceptual_planning_agent",
      instruction: `
 ## SYNTHESIS ASSIGNMENT
 

package/.codex/skills/brainstorm-with-file/SKILL.md

@@ -20,7 +20,7 @@ Interactive brainstorming workflow with **documented thought evolution**. Expand
 
 **Codex-Specific Features**:
 - Parallel subagent execution via `spawn_agent` + batch `wait({ ids: [...] })`
-- Role loading via path (agent reads `~/.codex/agents/*.md` itself)
+- Role loading via TOML agent definition (agent_type parameter in spawn_agent)
 - Deep interaction with `send_input` for multi-round refinement within single agent
 - Explicit lifecycle management with `close_agent`
 
@@ -208,12 +208,10 @@ Generate key questions that guide the brainstorming exploration. Use a subagent
 
 ```javascript
 const vectorAgent = spawn_agent({
+  agent_type: "cli_explore_agent",
   message: `
 ## TASK ASSIGNMENT
 
-### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-
 ---
 
 ## Context
@@ -302,9 +300,9 @@ Spawn 3 perspective agents in parallel: Creative + Pragmatic + Systematic.
 
 | Perspective | Role File | Focus |
 |-------------|-----------|-------|
-| Creative | `~/.codex/agents/cli-explore-agent.md` | Innovation, cross-domain inspiration, challenging assumptions |
-| Pragmatic | `~/.codex/agents/cli-explore-agent.md` | Implementation feasibility, effort estimates, blockers |
-| Systematic | `~/.codex/agents/cli-explore-agent.md` | Problem decomposition, patterns, scalability |
+| Creative | `cli_explore_agent` | Innovation, cross-domain inspiration, challenging assumptions |
+| Pragmatic | `cli_explore_agent` | Implementation feasibility, effort estimates, blockers |
+| Systematic | `cli_explore_agent` | Problem decomposition, patterns, scalability |
 
 **Parallel Subagent Execution**:
 
@@ -353,13 +351,13 @@ const perspectives = [
 // Parallel spawn - all agents start immediately
 const agentIds = perspectives.map(perspective => {
   return spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Run: `ccw spec load --category "exploration planning"`
-3. Read project tech context from loaded specs
+1. Run: `ccw spec load --category "exploration planning"`
+2. Read project tech context from loaded specs
 
 ---
 
@@ -560,13 +558,13 @@ const deepDiveResult = wait({ ids: [perspectiveAgent], timeout_ms: 600000 })
 
 ```javascript
 const deepDiveAgent = spawn_agent({
+  agent_type: "cli_explore_agent",
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: ${sessionFolder}/perspectives.json (prior findings)
-3. Run: `ccw spec load --category "exploration planning"`
+1. Read: ${sessionFolder}/perspectives.json (prior findings)
+2. Run: `ccw spec load --category "exploration planning"`
 
 ---
 
@@ -606,12 +604,12 @@ When user selects "challenge", spawn a dedicated challenge agent.
 
 ```javascript
 const challengeAgent = spawn_agent({
+  agent_type: "cli_explore_agent",
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: ${sessionFolder}/perspectives.json (ideas to challenge)
+1. Read: ${sessionFolder}/perspectives.json (ideas to challenge)
 
 ---
 
@@ -659,12 +657,12 @@ When user selects "merge", synthesize complementary ideas.
 
 ```javascript
 const mergeAgent = spawn_agent({
+  agent_type: "cli_explore_agent",
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: ${sessionFolder}/perspectives.json (source ideas)
+1. Read: ${sessionFolder}/perspectives.json (source ideas)
 
 ---
 
@@ -888,7 +886,7 @@ Dimensions guide brainstorming scope and focus:
 ```javascript
 // Safe parallel execution with error handling
 try {
-  const agentIds = perspectives.map(p => spawn_agent({ message: buildPrompt(p) }))
+  const agentIds = perspectives.map(p => spawn_agent({ agent_type: "cli_explore_agent", message: buildPrompt(p) }))
 
   const results = wait({ ids: agentIds, timeout_ms: 600000 })
 
@@ -1014,7 +1012,7 @@ Final synthesis:
 
 ### Codex Subagent Best Practices
 
-1. **Role Path, Not Content**: Pass `~/.codex/agents/*.md` path in message, let agent read itself
+1. **Agent Type, Not Path**: Use `agent_type` parameter in spawn_agent, not manual file path reading
 2. **Parallel for Perspectives**: Use batch spawn + wait for 3 perspective agents
 3. **Delay close_agent for Refinement**: Keep perspective agents alive for `send_input` reuse
 4. **Batch wait**: Use `wait({ ids: [a, b, c] })` for parallel agents, not sequential waits

package/.codex/skills/clean/SKILL.md

@@ -159,12 +159,12 @@ let exploreAgent = null
 try {
   // Launch cli-explore-agent
   exploreAgent = spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS
-1. Read: ~/.codex/agents/cli-explore-agent.md
-2. Read: ${projectRoot}/.workflow/project-tech.json (if exists)
+1. Read: ${projectRoot}/.workflow/project-tech.json (if exists)
 
 ## Task Objective
 Discover stale artifacts for cleanup.

package/.codex/skills/issue-discover/SKILL.md

@@ -229,13 +229,13 @@ Create a new subagent with task assignment.
 
 ```javascript
 const agentId = spawn_agent({
+  agent_type: "{agent_type}",
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/{agent-type}.md (MUST read first)
-2. Execute: ccw spec load --category exploration
-3. Execute: ccw spec load --category debug (known issues cross-reference)
+1. Execute: ccw spec load --category exploration
+2. Execute: ccw spec load --category debug (known issues cross-reference)
 
 ## TASK CONTEXT
 ${taskContext}

package/.codex/skills/issue-discover/phases/02-discover.md

@@ -114,13 +114,13 @@ const perspectiveAgents = [];
 
 selectedPerspectives.forEach(perspective => {
   const agentId = spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: {projectRoot}/.workflow/project-tech.json
-3. Read: {projectRoot}/.workflow/specs/*.md
+1. Read: {projectRoot}/.workflow/project-tech.json
+2. Read: {projectRoot}/.workflow/specs/*.md
 
 ---
 
@@ -192,13 +192,13 @@ agentIds.forEach(id => close_agent({ id }));
 // Only spawn if perspective requires external research
 if (selectedPerspectives.includes('security') || selectedPerspectives.includes('best-practices') || args.external) {
   const exaAgentId = spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: {projectRoot}/.workflow/project-tech.json
-3. Read: {projectRoot}/.workflow/specs/*.md
+1. Read: {projectRoot}/.workflow/project-tech.json
+2. Read: {projectRoot}/.workflow/specs/*.md
 
 ---
 

package/.codex/skills/issue-discover/phases/03-discover-by-prompt.md

@@ -234,6 +234,7 @@ while (shouldContinue && iteration < maxIterations) {
 
   iterationPlan.dimensions.forEach(dimension => {
     const agentId = spawn_agent({
+      agent_type: "cli_explore_agent",
       message: buildDimensionPromptWithACE(dimension, iteration, cumulativeFindings, iterationAceResults, iterationDir)
     });
     dimensionAgents.push({ agentId, dimension });
@@ -413,12 +414,11 @@ function buildDimensionPromptWithACE(dimension, iteration, previousFindings, ace
   );
 
   return `
-## TASK ASSIGNMENT
+## TASK ASSIGNMENT (agent_type: cli_explore_agent)
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read: {projectRoot}/.workflow/project-tech.json
-3. Read: {projectRoot}/.workflow/specs/*.md
+1. Read: {projectRoot}/.workflow/project-tech.json
+2. Read: {projectRoot}/.workflow/specs/*.md
 
 ---
 

package/.codex/skills/parallel-dev-cycle/phases/02-agent-execution.md

@@ -80,12 +80,12 @@ Cross-reference the task description against these documents for completeness.
   const focusDirective = getAgentFocusDirective('ra', state)
 
   return spawn_agent({
+    agent_type: "requirements_analyst",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/requirements-analyst.md
-2. Read: ${projectRoot}/.workflow/project-tech.json (if exists)
+1. Read: ${projectRoot}/.workflow/project-tech.json (if exists)
 3. Read: ${projectRoot}/.workflow/specs/*.md (if exists)
 4. Read: ${projectRoot}/.workflow/.cycle/${cycleId}.progress/coordination/feedback.md (if exists)
 
@@ -163,12 +163,12 @@ PHASE_RESULT:
 ```javascript
 function spawnEPAgent(cycleId, state, progressDir) {
   return spawn_agent({
+    agent_type: "exploration_planner",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/exploration-planner.md
-2. Read: ${projectRoot}/.workflow/project-tech.json
+1. Read: ${projectRoot}/.workflow/project-tech.json
 3. Read: ${projectRoot}/.workflow/specs/*.md
 4. Read: ${progressDir}/ra/requirements.md
 
@@ -242,12 +242,12 @@ PHASE_RESULT:
 ```javascript
 function spawnCDAgent(cycleId, state, progressDir) {
   return spawn_agent({
+    agent_type: "code_developer",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/code-developer.md
-2. Read: ${progressDir}/ep/plan.json
+1. Read: ${progressDir}/ep/plan.json
 3. Read: ${progressDir}/ra/requirements.md
 
 ---
@@ -320,12 +320,12 @@ PHASE_RESULT:
 ```javascript
 function spawnVASAgent(cycleId, state, progressDir) {
   return spawn_agent({
+    agent_type: "validation_archivist",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/validation-archivist.md
-2. Read: ${progressDir}/cd/changes.log
+1. Read: ${progressDir}/cd/changes.log
 
 ---
 

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

@@ -50,7 +50,7 @@ Unified multi-dimensional code review orchestrator with dual-mode (session/modul
 3. **Progressive Phase Loading**: Phase docs are read on-demand when that phase executes, not all at once
 4. **Auto-Continue**: All phases run autonomously without user intervention between phases
 5. **Subagent Lifecycle**: Explicit lifecycle management with spawn_agent → wait → close_agent
-6. **Role Path Loading**: Subagent roles loaded via path reference in MANDATORY FIRST STEPS
+6. **Role via agent_type**: Subagent roles loaded via TOML `agent_type` parameter in spawn_agent (e.g., `"cli_explore_agent"`)
 7. **Optional Fix Pipeline**: Phase 6-9 triggered only by explicit `--fix` flag or user confirmation after Phase 5
 8. **Content Preservation**: All agent prompts, code, schemas preserved verbatim from source commands
 
@@ -298,12 +298,12 @@ Create a new subagent with task assignment.
 
 ```javascript
 const agentId = spawn_agent({
+  agent_type: "{agent_type}",  // TOML agent definition name (e.g., "cli_explore_agent")
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/{agent-type}.md (MUST read first)
-2. Execute: ccw spec load --category "exploration execution"
+1. Execute: ccw spec load --category "exploration execution"
 
 ---
 

package/.codex/skills/review-cycle/phases/02-parallel-review.md

@@ -85,17 +85,17 @@ const dimensions = ['security', 'architecture', 'quality', 'action-items', 'perf
 
 dimensions.forEach(dimension => {
   const agentId = spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read review state: ${reviewStateJsonPath}
-3. Get target files: Read resolved_files from review-state.json
-4. Validate file access: bash(ls -la ${targetFiles.join(' ')})
-5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
-6. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
-7. Execute: ccw spec load --category review (review standards and checklists)
+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)
+5. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+6. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -124,7 +124,7 @@ Use **Deep Scan mode** for this review:
 
 ## Expected Deliverables
 
-**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 5, follow schema exactly
+**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 4, follow schema exactly
 
 1. Dimension Results JSON: ${outputDir}/dimensions/${dimension}.json
 
@@ -207,18 +207,18 @@ const dimensions = ['security', 'architecture', 'quality', 'action-items', 'perf
 
 dimensions.forEach(dimension => {
   const agentId = spawn_agent({
+    agent_type: "cli_explore_agent",
     message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read session metadata: ${sessionMetadataPath}
-3. Read completed task summaries: bash(find ${summariesDir} -name "IMPL-*.md" -type f)
-4. Get changed files: bash(cd ${workflowDir} && git log --since="${sessionCreatedAt}" --name-only --pretty=format: | sort -u)
-5. Read review state: ${reviewStateJsonPath}
-6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
-7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
-8. Execute: ccw spec load --category review (review standards and checklists)
+1. Read session metadata: ${sessionMetadataPath}
+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)
+6. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+7. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -247,7 +247,7 @@ Use **Deep Scan mode** for this review:
 
 ## Expected Deliverables
 
-**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 6, follow schema exactly
+**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 5, follow schema exactly
 
 1. Dimension Results JSON: ${outputDir}/dimensions/${dimension}.json
 
@@ -326,18 +326,18 @@ reviewAgents.forEach(id => close_agent({ id }));
 ```javascript
 // Spawn deep-dive agent
 const deepDiveAgentId = spawn_agent({
+  agent_type: "cli_explore_agent",
   message: `
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS (Agent Execute)
-1. **Read role definition**: ~/.codex/agents/cli-explore-agent.md (MUST read first)
-2. Read original finding: ${dimensionJsonPath}
-3. Read affected file: ${file}
-4. Identify related code: bash(grep -r "import.*${basename(file)}" ${projectDir}/src --include="*.ts")
-5. Read test files: bash(find ${projectDir}/tests -name "*${basename(file, '.ts')}*" -type f)
-6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-deep-dive-results-schema.json (get output schema reference)
-7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints for remediation)
-8. Execute: ccw spec load --category review (review standards and checklists)
+1. Read original finding: ${dimensionJsonPath}
+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)
+6. Execute: ccw spec load --category "exploration execution" (technology stack and constraints for remediation)
+7. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -372,7 +372,7 @@ Then apply **Deep Scan mode** for semantic analysis:
 
 ## Expected Deliverables
 
-**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 6, follow schema exactly
+**Schema Reference**: Schema obtained in MANDATORY FIRST STEPS step 5, follow schema exactly
 
 1. Deep-Dive Results JSON: ${outputDir}/iterations/iteration-${iteration}-finding-${findingId}.json