refactor(workflow): rename workflow-lite-plan to workflow-lite-planex and remove standalone lite-execute

- Rename skill directory from workflow-lite-plan to workflow-lite-planex (planex = plan + execute)
- Remove standalone lite-execute command entry from command.json and analyze_commands.py
- Update all 60+ files referencing workflow-lite-plan to use workflow-lite-planex
- Update descriptions to clarify Phase 1: plan → Phase 2: execute architecture
- Remove lite-execute as standalone command from orchestrator routing tables
- Update docs (EN/ZH) to reflect unified planex naming and phase descriptions

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

@@ -1,27 +1,26 @@
 ---
 name: workflow-multi-cli-plan
-description: Multi-CLI collaborative planning and execution skill - route to multi-cli-plan or lite-execute with prompt enhancement. Triggers on "workflow-multi-cli-plan", "workflow:lite-execute".
+description: Multi-CLI collaborative planning and execution skill with integrated execution phase. Triggers on "workflow-multi-cli-plan".
 allowed-tools: Skill, Task, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep, mcp__ace-tool__search_context
 ---
 
 # Workflow Multi-CLI Plan
 
-Unified multi-CLI collaborative planning and execution skill. Routes to multi-cli-plan (ACE context + multi-CLI discussion + plan generation) or lite-execute (execution engine) based on trigger, with prompt enhancement for both modes.
+Unified multi-CLI collaborative planning and execution skill. Routes to multi-cli-plan (ACE context + multi-CLI discussion + plan generation) which then hands off to lite-execute (Phase 2) internally for execution.
 
 ## Architecture Overview
 
 ```
 ┌─────────────────────────────────────────────────────────┐
 │  SKILL.md (Router + Prompt Enhancement)                  │
-│  → Detect mode → Enhance prompt → Dispatch to phase     │
+│  → Enhance prompt → Dispatch to Phase 1                 │
 └──────────────────────┬──────────────────────────────────┘
                        │
-           ┌───────────┼───────────┐
-           ↓                       ↓
+                       ↓
      ┌──────────────┐        ┌───────────┐
      │multi-cli-plan│        │lite-execute│
-     │   Phase 1    │        │  Phase 2   │
-     │  Plan+Exec   │─handoff→│ Standalone │
+     │   Phase 1    │─handoff→│  Phase 2   │
+     │  Plan+Exec   │        │ (internal) │
      └──────────────┘        └───────────┘
 ```
 
@@ -29,12 +28,7 @@ Unified multi-CLI collaborative planning and execution skill. Routes to multi-cl
 
 ```javascript
 const args = $ARGUMENTS
-const mode = detectMode()
-
-function detectMode() {
-  if (skillName === 'workflow:lite-execute') return 'execute'
-  return 'plan'  // default: workflow-multi-cli-plan
-}
+const mode = 'plan'  // workflow-multi-cli-plan always starts with planning
 ```
 
 **Routing Table**:
@@ -42,7 +36,6 @@ function detectMode() {
 | Trigger | Mode | Phase Document | Description |
 |---------|------|----------------|-------------|
 | `workflow-multi-cli-plan` | plan | [phases/01-multi-cli-plan.md](phases/01-multi-cli-plan.md) | Multi-CLI collaborative planning (ACE context → discussion → plan → execute) |
-| `workflow:lite-execute` | execute | [phases/02-lite-execute.md](phases/02-lite-execute.md) | Standalone execution (in-memory / prompt / file) |
 
 ## Interactive Preference Collection
 
@@ -72,24 +65,6 @@ if (autoYes) {
   workflowPreferences = {
     autoYes: prefResponse.autoMode === 'Auto'
   }
-} else {
-  // Execute mode
-  const prefResponse = AskUserQuestion({
-    questions: [
-      {
-        question: "是否跳过所有确认步骤（自动模式）？",
-        header: "Auto Mode",
-        multiSelect: false,
-        options: [
-          { label: "Interactive (Recommended)", description: "交互模式，包含确认步骤" },
-          { label: "Auto", description: "跳过所有确认，自动执行" }
-        ]
-      }
-    ]
-  })
-  workflowPreferences = {
-    autoYes: prefResponse.autoMode === 'Auto'
-  }
 }
 ```
 
@@ -106,12 +81,9 @@ Bash('ccw spec load --category planning')
 // Step 2: Log available context
 console.log('Project context loaded via: ccw spec load --category planning')
 
-// Step 3: Dispatch to phase (workflowPreferences available as context)
-if (mode === 'plan') {
-  // Read phases/01-multi-cli-plan.md and execute
-} else {
-  // Read phases/02-lite-execute.md and execute
-}
+// Step 3: Dispatch to Phase 1 (workflowPreferences available as context)
+// Read phases/01-multi-cli-plan.md and execute
+// Phase 1 internally hands off to Phase 2 (lite-execute) after plan approval
 ```
 
 ## Compact Recovery (Phase Persistence)
@@ -134,21 +106,9 @@ Multi-phase execution (multi-cli-plan → lite-execute) spans long conversations
 5. Phase 5 directly reads and executes Phase 2 (lite-execute) with executionContext
 ```
 
-### Execute Mode (workflow:lite-execute)
-
-```
-1. Collect preferences via AskUserQuestion (autoYes)
-2. Enhance prompt with project context availability
-3. Read phases/02-lite-execute.md
-4. Execute lite-execute pipeline (input detection → execution → review)
-```
-
 ## Usage
 
-Plan mode and execute mode are triggered by skill name routing (see Mode Detection). Workflow preferences (auto mode) are collected interactively via AskUserQuestion before dispatching to phases.
-
-**Plan mode**: Task description provided as arguments → interactive preference collection → multi-CLI planning pipeline
-**Execute mode**: Task description, file path, or in-memory context → interactive preference collection → execution pipeline
+Task description provided as arguments → interactive preference collection → multi-CLI planning pipeline → internal execution handoff to Phase 2 (lite-execute).
 
 ## Phase Reference Documents
 

.claude/skills/workflow-multi-cli-plan/phases/01-multi-cli-plan.md

@@ -24,7 +24,7 @@ When `workflowPreferences.autoYes` is true: Auto-approve plan, use recommended s
 **Output Directory**: `.workflow/.multi-cli-plan/{session-id}/`
 **Default Max Rounds**: 3 (convergence may complete earlier)
 **CLI Tools**: @cli-discuss-agent (analysis), @cli-lite-planning-agent (plan generation)
-**Execution**: Auto-hands off to `/workflow:lite-execute --in-memory` after plan approval
+**Execution**: Auto-hands off to Phase 2 (lite-execute) after plan approval
 
 ## What & Why
 
@@ -81,7 +81,7 @@ Phase 4: User Decision
 Phase 5: Plan Generation & Execution Handoff
    ├─ Generate plan.json + .task/*.json (via @cli-lite-planning-agent, two-layer output)
    ├─ Build executionContext with user selections and taskFiles
-   └─ Execute to /workflow:lite-execute --in-memory
+   └─ Execute via Phase 2 (lite-execute)
 ```
 
 ### Agent Roles
@@ -598,7 +598,7 @@ TodoWrite({ todos: [
 
 ```bash
 # Simpler single-round planning
-/workflow-lite-plan "task description"
+/workflow-lite-planex "task description"
 
 # Issue-driven discovery
 /issue:discover-by-prompt "find issues"
@@ -609,7 +609,7 @@ cat .workflow/.multi-cli-plan/{session-id}/rounds/1/synthesis.json
 cat .workflow/.multi-cli-plan/{session-id}/context-package.json
 
 # Direct execution (if you have plan.json)
-/workflow:lite-execute plan.json
+# Use workflow-lite-planex or workflow-multi-cli-plan (execution is integrated)
 ```
 
 ## Next Phase

.claude/skills/workflow-multi-cli-plan/phases/02-lite-execute.md

@@ -26,22 +26,13 @@ Flexible task execution command supporting three input modes: in-memory plan (fr
 
 ## Usage
 
-### Command Syntax
-```bash
-/workflow:lite-execute [FLAGS] <INPUT>
-
-# Flags
---in-memory                Use plan from memory (called by lite-plan)
-
-# Arguments
-<input>                    Task description string, or path to file (required)
-```
+> **Note**: This is an internal phase, not a standalone command. It is called by Phase 1 (multi-cli-plan) after plan approval, or by lite-plan after Phase 4 approval.
 
 ## Input Modes
 
 ### Mode 1: In-Memory Plan
 
-**Trigger**: Called by lite-plan after Phase 4 approval with `--in-memory` flag
+**Trigger**: Called by multi-cli-plan Phase 5 after plan approval, or by lite-plan after Phase 4 approval
 
 **Input Source**: `executionContext` global variable set by lite-plan