Refactor code structure for improved readability and maintainability

.claude/commands/workflow/tools/code-validation-gate.md

@@ -354,7 +354,7 @@ When used in test-fix workflow, generates task:
     "requirements": "Validate generated code for AI common errors"
   },
   "flow_control": {
-    "validation_config": "~/.claude/workflows/test-quality-config.json",
+    "validation_config": "~/.ccw/workflows/test-quality-config.json",
     "max_retries": 2,
     "auto_fix_enabled": true
   },

.claude/commands/workflow/tools/conflict-resolution.md

@@ -129,7 +129,7 @@ Task(subagent_type="cli-execution-agent", run_in_background=false, prompt=`
   ## Analysis Steps
 
   ### 0. Load Output Schema (MANDATORY)
-  Execute: cat ~/.claude/workflows/cli-templates/schemas/conflict-resolution-schema.json
+  Execute: cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json
 
   ### 1. Load Context
   - Read existing files from conflict_detection.existing_files
@@ -178,7 +178,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 ~/.claude/workflows/cli-templates/schemas/conflict-resolution-schema.json\` to get full schema
+  **Schema Reference**: Execute \`cat ~/.ccw/workflows/cli-templates/schemas/conflict-resolution-schema.json\` to get full schema
 
   Return JSON following the schema above. Key requirements:
   - Minimum 2 strategies per conflict, max 4

.claude/commands/workflow/tools/context-gather.md

@@ -137,7 +137,7 @@ Execute **${angle}** exploration for task planning context. Analyze codebase fro
 **You (cli-explore-agent) MUST execute these steps in order:**
 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 ~/.claude/workflows/cli-templates/schemas/explore-json-schema.json (get output schema reference)
+3. Execute: cat ~/.ccw/workflows/cli-templates/schemas/explore-json-schema.json (get output schema reference)
 
 ## Exploration Strategy (${angle} focus)
 

.claude/commands/workflow/tools/task-generate-tdd.md

@@ -439,7 +439,7 @@ IMPORTANT: Do NOT add command field to implementation_approach steps. Execution
 
 ##### 2. IMPL_PLAN.md (TDD Variant)
 - **Location**: `.workflow/active/{session-id}/IMPL_PLAN.md`
-- **Template**: `~/.claude/workflows/cli-templates/prompts/workflow/impl-plan-template.txt`
+- **Template**: `~/.ccw/workflows/cli-templates/prompts/workflow/impl-plan-template.txt`
 - **TDD-Specific Frontmatter**: workflow_type="tdd", tdd_workflow=true, feature_count, task_breakdown
 - **TDD Implementation Tasks Section**: Feature-by-feature with internal Red-Green-Refactor cycles
 - **Context Analysis**: Artifact references and exploration insights

.claude/commands/workflow/tools/test-concept-enhanced.md

@@ -86,7 +86,7 @@ Analyze test requirements and generate comprehensive test generation strategy us
 Session: {test_session_id}
 Source Session: {source_session_id}
 Working Dir: .workflow/active/{test_session_id}/.process
-Template: ~/.claude/workflows/cli-templates/prompts/test/test-concept-analysis.txt
+Template: ~/.ccw/workflows/cli-templates/prompts/test/test-concept-analysis.txt
 
 ## EXECUTION STEPS
 1. Execute Gemini analysis:

.claude/commands/workflow/tools/test-task-generate.md

@@ -155,7 +155,7 @@ Write(testPlanningNotesPath, `# Test Planning Notes
 **Execution Steps**:
 1. Load TEST_ANALYSIS_RESULTS.md from `.workflow/active/{test-session-id}/.process/`
 2. Invoke `cli-execution-agent` with Gemini for test enhancement analysis
-3. Use template: `~/.claude/workflows/cli-templates/prompts/test-suggestions-enhancement.txt`
+3. Use template: `~/.ccw/workflows/cli-templates/prompts/test-suggestions-enhancement.txt`
 4. Gemini generates enriched test suggestions across L1-L3 layers → gemini-enriched-suggestions.md
 5. Record enriched suggestions to test-planning-notes.md (Gemini Enhancement section)