Refactor workflow output paths to use a standardized sessions directory structure

- Updated output paths in various command files to reflect the new structure: `.workflow/sessions/{session_id}/` instead of `.workflow/{session_id}/`.
- Adjusted documentation and code comments to ensure consistency across all agents and commands.
- Ensured that all references to session-related files are correctly pointing to the new directory format.

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

@@ -5,7 +5,7 @@ Validate technical feasibility and identify implementation risks for proposed so
 □ Assess complexity, validate technology choices
 □ Evaluate performance and security implications
 □ Focus on TECHNICAL FEASIBILITY and RISK ASSESSMENT
-□ Write output to specified .workflow/{session_id}/.process/ path
+□ Write output to specified .workflow/sessions/{session_id}/.process/ path
 
 ## PREREQUISITE ANALYSIS
 
@@ -94,7 +94,7 @@ Review Gemini's proposed code targets:
 ## OUTPUT REQUIREMENTS
 
 ### Output File
-**Path**: `.workflow/{session_id}/.process/codex-feasibility-validation.md`
+**Path**: `.workflow/sessions/{session_id}/.process/codex-feasibility-validation.md`
 **Format**: Follow structure from `~/.claude/workflows/cli-templates/prompts/workflow/analysis-results-structure.txt`
 
 ### Required Sections
@@ -171,6 +171,6 @@ Rate each aspect on 1-5 scale:
 □ Risk mitigation strategies provided
 □ Resource requirements estimated
 □ Final feasibility judgment (PROCEED/RECONSIDER/REJECT)
-□ Output written to .workflow/{session_id}/.process/codex-feasibility-validation.md
+□ Output written to .workflow/sessions/{session_id}/.process/codex-feasibility-validation.md
 
 Focus: Technical feasibility validation with realistic risk assessment and mitigation strategies.

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

@@ -5,7 +5,7 @@ Analyze and design optimal solution with comprehensive architecture evaluation a
 □ 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/{session_id}/.process/ path
+□ Write output to specified .workflow/sessions/{session_id}/.process/ path
 
 ## ANALYSIS PRIORITY
 
@@ -73,7 +73,7 @@ For each target:
 ## OUTPUT REQUIREMENTS
 
 ### Output File
-**Path**: `.workflow/{session_id}/.process/gemini-solution-design.md`
+**Path**: `.workflow/sessions/{session_id}/.process/gemini-solution-design.md`
 **Format**: Follow structure from `~/.claude/workflows/cli-templates/prompts/workflow/analysis-results-structure.txt`
 
 ### Required Sections
@@ -126,6 +126,6 @@ If brainstorming artifacts exist:
 □ Code targets specified in correct format
 □ Feasibility scores provided (X/5)
 □ Final recommendation (PROCEED/RECONSIDER/REJECT)
-□ Output written to .workflow/{session_id}/.process/gemini-solution-design.md
+□ Output written to .workflow/sessions/{session_id}/.process/gemini-solution-design.md
 
 Focus: Comprehensive solution design emphasizing architecture decisions and critical insights.

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

@@ -6,9 +6,9 @@ IMPL_PLAN.md Template - Implementation Plan Document Structure
 ---
 identifier: WFS-{session-id}
 source: "User requirements" | "File: path" | "Issue: ISS-001"
-analysis: .workflow/{session-id}/.process/ANALYSIS_RESULTS.md
-artifacts: .workflow/{session-id}/.brainstorming/
-context_package: .workflow/{session-id}/.process/context-package.json  # CCW smart context
+analysis: .workflow/sessions//{session-id}/.process/ANALYSIS_RESULTS.md
+artifacts: .workflow/sessions//{session-id}/.brainstorming/
+context_package: .workflow/sessions//{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"