Workflow Multi-CLI Plan

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)                  │
│  → Enhance prompt → Dispatch to Phase 1                 │
└──────────────────────┬──────────────────────────────────┘
                       │
                       ↓
     ┌──────────────┐        ┌───────────┐
     │multi-cli-plan│        │lite-execute│
     │   Phase 1    │─handoff→│  Phase 2   │
     │  Plan+Exec   │        │ (internal) │
     └──────────────┘        └───────────┘

Mode Detection & Routing

javascript
1const args = $ARGUMENTS
2const mode = 'plan'  // workflow-multi-cli-plan always starts with planning

Routing Table:

Interactive Preference Collection

Before dispatching, collect workflow preferences via AskUserQuestion:

javascript
1// ★ 统一 auto mode 检测：-y/--yes 从 $ARGUMENTS 或 ccw 传播
2const autoYes = /\b(-y|--yes)\b/.test($ARGUMENTS)
3
4if (autoYes) {
5  // 自动模式：跳过所有询问，使用默认值
6  workflowPreferences = { autoYes: true }
7} else if (mode === 'plan') {
8  const prefResponse = AskUserQuestion({
9    questions: [
10      {
11        question: "是否跳过所有确认步骤（自动模式）？",
12        header: "Auto Mode",
13        multiSelect: false,
14        options: [
15          { label: "Interactive (Recommended)", description: "交互模式，包含确认步骤" },
16          { label: "Auto", description: "跳过所有确认，自动执行" }
17        ]
18      }
19    ]
20  })
21  workflowPreferences = {
22    autoYes: prefResponse.autoMode === 'Auto'
23  }
24}

workflowPreferences is passed to phase execution as context variable, referenced as workflowPreferences.autoYes within phases.

Prompt Enhancement

After collecting preferences, enhance context and dispatch:

javascript
1// Step 1: Load project context via ccw spec
2Bash('ccw spec load --category planning')
3
4// Step 2: Log available context
5console.log('Project context loaded via: ccw spec load --category planning')
6
7// Step 3: Dispatch to Phase 1 (workflowPreferences available as context)
8// Read phases/01-multi-cli-plan.md and execute
9// Phase 1 internally hands off to Phase 2 (lite-execute) after plan approval

Compact Recovery (Phase Persistence)

Multi-phase execution (multi-cli-plan → lite-execute) spans long conversations. Uses 双重保险: TodoWrite 跟踪 active phase 保护其不被压缩，sentinel 作为兜底。

⚠️ COMPACT DIRECTIVE: Context compression MUST check TodoWrite phase status. The phase currently marked in_progress is the active execution phase — preserve its FULL content. Only compress phases marked completed or pending.

Execution Flow

Plan Mode (workflow-multi-cli-plan)

1. Collect preferences via AskUserQuestion (autoYes)
2. Enhance prompt with project context availability
3. Read phases/01-multi-cli-plan.md
4. Execute multi-cli-plan pipeline (Phase 1-5 within the phase doc)
5. Phase 5 directly reads and executes Phase 2 (lite-execute) with executionContext

Usage

Task description provided as arguments → interactive preference collection → multi-CLI planning pipeline → internal execution handoff to Phase 2 (lite-execute).

Phase Reference Documents

Compact Rules:

1. TodoWrite in_progress → 保留完整内容，禁止压缩
2. TodoWrite completed → 可压缩为摘要
3. 🔄 sentinel fallback → Phase 2 包含 compact sentinel；若 compact 后仅存 sentinel 而无完整 Step 协议，必须立即 Read("phases/02-lite-execute.md") 恢复