refactor: Add tree-style execution flow diagrams to all workflow commands

Added tree-style execution process diagrams using ASCII art (├─, └─, │) to 34 workflow command files across three directories for improved readability and execution flow clarity.

## Changes by Directory

### workflow/ root (17 files)
- lite-plan.md, lite-execute.md, lite-fix.md
- plan.md, execute.md, replan.md
- status.md, review.md, review-fix.md
- review-session-cycle.md, review-module-cycle.md
- session commands (start, complete, resume, list)
- tdd-plan.md, tdd-verify.md, test-cycle-execute.md, test-gen.md, test-fix-gen.md

### workflow/ui-design/ (10 files)
- layout-extract.md, animation-extract.md, style-extract.md
- generate.md, import-from-code.md, codify-style.md
- imitate-auto.md, explore-auto.md
- reference-page-generator.md, design-sync.md

### workflow/tools/ (8 files)
- conflict-resolution.md, task-generate-agent.md, context-gather.md
- tdd-coverage-analysis.md, task-generate-tdd.md
- test-task-generate.md, test-concept-enhanced.md, test-context-gather.md

## Diagram Features
- Input parsing with flag enumeration
- Decision branching with conditional paths
- Phase/step hierarchy with clear nesting
- Mode detection and validation flows

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/workflow/lite-execute.md

@@ -138,26 +138,29 @@ If `isPlanJson === false`:
 
 ## Execution Process
 
-### Workflow Overview
-
 ```
-Input Processing → Mode Detection
-    |
-    v
-[Mode 1] --in-memory: Load executionContext → Skip selection
-[Mode 2] Prompt: Create plan → User selects method + review
-[Mode 3] File: Detect format → Extract plan OR treat as prompt → User selects
-    |
-    v
-Execution & Progress Tracking
-    ├─ Step 1: Initialize execution tracking
-    ├─ Step 2: Create TodoWrite execution list
-    ├─ Step 3: Launch execution (Agent or Codex)
-    ├─ Step 4: Track execution progress
-    └─ Step 5: Code review (optional)
-    |
-    v
-Execution Complete
+Input Parsing:
+   └─ Decision (mode detection):
+      ├─ --in-memory flag → Mode 1: Load executionContext → Skip user selection
+      ├─ Ends with .md/.json/.txt → Mode 3: Read file → Detect format
+      │   ├─ Valid plan.json → Use planObject → User selects method + review
+      │   └─ Not plan.json → Treat as prompt → User selects method + review
+      └─ Other → Mode 2: Prompt description → User selects method + review
+
+Execution:
+   ├─ Step 1: Initialize result tracking (previousExecutionResults = [])
+   ├─ Step 2: Task grouping & batch creation
+   │   ├─ Infer dependencies (same file → sequential, keywords → sequential)
+   │   ├─ Group into batches (parallel: independent, sequential: dependent)
+   │   └─ Create TodoWrite list for batches
+   ├─ Step 3: Launch execution
+   │   ├─ Phase 1: All parallel batches (⚡ concurrent via multiple tool calls)
+   │   └─ Phase 2: Sequential batches (→ one by one)
+   ├─ Step 4: Track progress (TodoWrite updates per batch)
+   └─ Step 5: Code review (if codeReviewTool ≠ "Skip")
+
+Output:
+   └─ Execution complete with results in previousExecutionResults[]
 ```
 
 ## Detailed Execution Steps
@@ -453,9 +456,16 @@ Complexity: ${planObject.complexity}
 **Execution with tracking**:
 ```javascript
 // Launch CLI in foreground (NOT background)
+// Timeout based on complexity: Low=40min, Medium=60min, High=100min
+const timeoutByComplexity = {
+  "Low": 2400000,    // 40 minutes
+  "Medium": 3600000, // 60 minutes
+  "High": 6000000    // 100 minutes
+}
+
 bash_result = Bash(
   command=cli_command,
-  timeout=6000000 
+  timeout=timeoutByComplexity[planObject.complexity] || 3600000
 )
 
 // Update TodoWrite when execution completes