workflow-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Workflow Plan

工作流规划

Unified planning skill combining 4-phase planning workflow, plan quality verification, and interactive replanning. Produces IMPL_PLAN.md, task JSONs, verification reports, and manages plan lifecycle through session-level artifact updates.
统一规划Skill,整合了四阶段规划工作流、计划质量验证和交互式重规划功能。可生成IMPL_PLAN.md、任务JSON文件、验证报告,并通过会话级工件更新管理计划生命周期。

Architecture Overview

架构概览

┌──────────────────────────────────────────────────────────────────┐
│  Workflow Plan Orchestrator (SKILL.md)                            │
│  → Route by mode: plan | verify | replan                         │
│  → Pure coordinator: Execute phases, parse outputs, pass context │
└──────────────────────────────┬───────────────────────────────────┘
        ┌───────────────────────┼───────────────────────┐
        ↓                       ↓                       ↓
  ┌───────────┐          ┌───────────┐           ┌───────────┐
  │ Plan Mode │          │  Verify   │           │  Replan   │
  │ (default) │          │   Mode    │           │   Mode    │
  │ Phase 1-4 │          │  Phase 5  │           │  Phase 6  │
  └─────┬─────┘          └───────────┘           └───────────┘
    ┌───┼───┬───┐
    ↓   ↓   ↓   ↓
  ┌───┐┌───┐┌───┐┌───┐
  │ 1 ││ 2 ││ 3 ││ 4 │
  │Ses││Ctx││Con││Gen│
  └───┘└───┘└───┘└─┬─┘
              ┌───────────┐
              │ Confirm   │─── Verify ──→ Phase 5
              │ (choice)  │─── Execute ─→ Skill("workflow-execute")
              └───────────┘─── Review ──→ Display session status inline
┌──────────────────────────────────────────────────────────────────┐
│  Workflow Plan Orchestrator (SKILL.md)                            │
│  → 按模式路由:plan | verify | replan                         │
│  → 纯协调器:执行阶段、解析输出、传递上下文 │
└──────────────────────────────┬───────────────────────────────────┘
        ┌───────────────────────┼───────────────────────┐
        ↓                       ↓                       ↓
  ┌───────────┐          ┌───────────┐           ┌───────────┐
  │ Plan模式 │          │  Verify   │           │  Replan   │
  │(默认)│          │   模式    │           │   模式    │
  │ 阶段1-4 │          │  阶段5  │           │  阶段6  │
  └─────┬─────┘          └───────────┘           └───────────┘
    ┌───┼───┬───┐
    ↓   ↓   ↓   ↓
  ┌───┐┌───┐┌───┐┌───┐
  │ 1 ││ 2 ││ 3 ││ 4 │
  │会话││上下文││冲突││生成│
  └───┘└───┘└───┘└─┬─┘
              ┌───────────┐
              │ 确认   │─── 验证 ──→ 阶段5
              │(选择)│─── 执行 ─→ Skill("workflow-execute")
              └───────────┘─── 查看 ──→ 内联显示会话状态

Key Design Principles

核心设计原则

  1. Pure Orchestrator: SKILL.md routes and coordinates only; execution detail lives in phase files
  2. Progressive Phase Loading: Read phase docs ONLY when that phase is about to execute
  3. Multi-Mode Routing: Single skill handles plan/verify/replan via mode detection
  4. Task Attachment Model: Sub-command tasks are ATTACHED, executed sequentially, then COLLAPSED
  5. Auto-Continue: After each phase completes, automatically execute next pending phase
  6. Accumulated State: planning-notes.md carries context across phases for N+1 decisions
  1. 纯协调器:SKILL.md仅负责路由和协调,执行细节存储在阶段文件中
  2. 渐进式阶段加载:仅在即将执行某阶段时才读取该阶段的文档
  3. 多模式路由:单个Skill通过模式检测处理规划/验证/重规划操作
  4. 任务附加模型:子命令任务会被附加到当前工作流,按顺序执行后再折叠
  5. 自动续行:每个阶段完成后,自动执行下一个待处理阶段
  6. 累积状态:planning-notes.md在各阶段间传递上下文,支持后续决策

Interactive Preference Collection

交互式偏好收集

Before dispatching to phase execution, collect workflow preferences via AskUserQuestion:
javascript
const prefResponse = AskUserQuestion({
  questions: [
    {
      question: "是否跳过所有确认步骤(自动模式)?",
      header: "Auto Mode",
      multiSelect: false,
      options: [
        { label: "Interactive (Recommended)", description: "交互模式,包含确认步骤" },
        { label: "Auto", description: "跳过所有确认,自动执行" }
      ]
    }
  ]
})

workflowPreferences = {
  autoYes: prefResponse.autoMode === 'Auto'
}

// For replan mode, also collect interactive preference
if (mode === 'replan') {
  const replanPref = AskUserQuestion({
    questions: [
      {
        question: "是否使用交互式澄清模式?",
        header: "Replan Mode",
        multiSelect: false,
        options: [
          { label: "Standard (Recommended)", description: "使用安全默认值" },
          { label: "Interactive", description: "通过提问交互式澄清修改范围" }
        ]
      }
    ]
  })
  workflowPreferences.interactive = replanPref.replanMode === 'Interactive'
}
workflowPreferences is passed to phase execution as context variable, referenced as
workflowPreferences.autoYes
,
workflowPreferences.interactive
within phases.
在分发到阶段执行前,通过AskUserQuestion收集工作流偏好:
javascript
const prefResponse = AskUserQuestion({
  questions: [
    {
      question: "是否跳过所有确认步骤(自动模式)?",
      header: "Auto Mode",
      multiSelect: false,
      options: [
        { label: "Interactive (Recommended)", description: "交互模式,包含确认步骤" },
        { label: "Auto", description: "跳过所有确认,自动执行" }
      ]
    }
  ]
})

workflowPreferences = {
  autoYes: prefResponse.autoMode === 'Auto'
}

// 重规划模式下,额外收集交互偏好
if (mode === 'replan') {
  const replanPref = AskUserQuestion({
    questions: [
      {
        question: "是否使用交互式澄清模式?",
        header: "Replan Mode",
        multiSelect: false,
        options: [
          { label: "Standard (Recommended)", description: "使用安全默认值" },
          { label: "Interactive", description: "通过提问交互式澄清修改范围" }
        ]
      }
    ]
  })
  workflowPreferences.interactive = replanPref.replanMode === 'Interactive'
}
workflowPreferences 会作为上下文变量传递给阶段执行,在阶段内可通过
workflowPreferences.autoYes
workflowPreferences.interactive
进行引用。

Mode Detection

模式检测

javascript
const args = $ARGUMENTS
const mode = detectMode(args)

function detectMode(args) {
  // Skill trigger determines mode
  if (skillName === 'workflow:plan-verify') return 'verify'
  if (skillName === 'workflow:replan') return 'replan'
  return 'plan'  // default: workflow:plan
}
javascript
const args = $ARGUMENTS
const mode = detectMode(args)

function detectMode(args) {
  // Skill触发词决定模式
  if (skillName === 'workflow:plan-verify') return 'verify'
  if (skillName === 'workflow:replan') return 'replan'
  return 'plan'  // 默认:workflow:plan
}

Execution Flow

执行流程

Plan Mode (default)

Plan模式(默认)

Input Parsing:
   └─ Convert user input to structured format (GOAL/SCOPE/CONTEXT)

Phase 1: Session Discovery
   └─ Ref: phases/01-session-discovery.md
      └─ Output: sessionId (WFS-xxx), planning-notes.md

Phase 2: Context Gathering
   └─ Ref: phases/02-context-gathering.md
      ├─ Tasks attached: Analyze structure → Identify integration → Generate package
      └─ Output: contextPath + conflictRisk

Phase 3: Conflict Resolution (conditional: conflictRisk ≥ medium)
   └─ Decision (conflictRisk check):
      ├─ conflictRisk ≥ medium → Ref: phases/03-conflict-resolution.md
      │   ├─ Tasks attached: Detect conflicts → Present to user → Apply strategies
      │   └─ Output: Modified brainstorm artifacts
      └─ conflictRisk < medium → Skip to Phase 4

Phase 4: Task Generation
   └─ Ref: phases/04-task-generation.md
      └─ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md

Plan Confirmation (User Decision Gate):
   └─ Decision (user choice):
      ├─ "Verify Plan Quality" (Recommended) → Route to Phase 5 (plan-verify)
      ├─ "Start Execution" → Skill(skill="workflow-execute")
      └─ "Review Status Only" → Display session status inline
输入解析:
   └─ 将用户输入转换为结构化格式(GOAL/SCOPE/CONTEXT)

阶段1:会话发现
   └─ 参考:phases/01-session-discovery.md
      └─ 输出:sessionId(WFS-xxx)、planning-notes.md

阶段2:上下文收集
   └─ 参考:phases/02-context-gathering.md
      ├─ 附加任务:分析结构 → 识别集成点 → 生成包
      └─ 输出:contextPath + conflictRisk

阶段3:冲突解决(条件触发:conflictRisk ≥ medium)
   └─ 决策(基于conflictRisk检查):
      ├─ conflictRisk ≥ medium → 参考:phases/03-conflict-resolution.md
      │   ├─ 附加任务:检测冲突 → 呈现给用户 → 应用解决策略
      │   └─ 输出:修改后的头脑风暴工件
      └─ conflictRisk < medium → 跳过至阶段4

阶段4:任务生成
   └─ 参考:phases/04-task-generation.md
      └─ 输出:IMPL_PLAN.md、任务JSON文件、TODO_LIST.md

计划确认(用户决策节点):
   └─ 决策(用户选择):
      ├─ "验证计划质量"(推荐)→ 路由至阶段5(plan-verify)
      ├─ "开始执行" → Skill(skill="workflow-execute")
      └─ "仅查看状态" → 内联显示会话状态

Verify Mode

Verify模式

Phase 5: Plan Verification
   └─ Ref: phases/05-plan-verify.md
      └─ Output: PLAN_VERIFICATION.md with quality gate recommendation
阶段5:计划验证
   └─ 参考:phases/05-plan-verify.md
      └─ 输出:带有质量门建议的PLAN_VERIFICATION.md

Replan Mode

Replan模式

Phase 6: Interactive Replan
   └─ Ref: phases/06-replan.md
      └─ Output: Updated IMPL_PLAN.md, task JSONs, TODO_LIST.md
Phase Reference Documents (read on-demand when phase executes):
PhaseDocumentPurposeMode
1phases/01-session-discovery.mdCreate or discover workflow sessionplan
2phases/02-context-gathering.mdGather project context and analyze codebaseplan
3phases/03-conflict-resolution.mdDetect and resolve conflicts (conditional)plan
4phases/04-task-generation.mdGenerate implementation plan and task JSONsplan
5phases/05-plan-verify.mdRead-only verification with quality gateverify
6phases/06-replan.mdInteractive replanning with boundary clarificationreplan
阶段6:交互式重规划
   └─ 参考:phases/06-replan.md
      └─ 输出:更新后的IMPL_PLAN.md、任务JSON文件、TODO_LIST.md
阶段参考文档(仅在即将执行该阶段时读取):
阶段文档用途模式
1phases/01-session-discovery.md创建或发现工作流会话plan
2phases/02-context-gathering.md收集项目上下文并分析代码库plan
3phases/03-conflict-resolution.md检测并解决冲突(条件触发)plan
4phases/04-task-generation.md生成实施计划和任务JSON文件plan
5phases/05-plan-verify.md只读验证并提供质量门建议verify
6phases/06-replan.md交互式重规划,含边界澄清replan

Core Rules

核心规则

  1. Start Immediately: First action is mode detection + TodoWrite initialization, second action is phase execution
  2. No Preliminary Analysis: Do not read files, analyze structure, or gather context before Phase 1
  3. Parse Every Output: Extract required data from each phase output for next phase
  4. Auto-Continue via TodoList: Check TodoList status to execute next pending phase automatically
  5. Track Progress: Update TodoWrite dynamically with task attachment/collapse pattern
  6. Task Attachment Model: Skill execute attaches sub-tasks to current workflow. Orchestrator executes these attached tasks itself, then collapses them after completion
  7. Progressive Phase Loading: Read phase docs ONLY when that phase is about to execute
  8. DO NOT STOP: Continuous multi-phase workflow. After executing all attached tasks, immediately collapse them and execute next phase
  1. 立即启动:第一个操作是模式检测 + TodoWrite初始化,第二个操作是阶段执行
  2. 无前置分析:在阶段1之前,不得读取文件、分析结构或收集上下文
  3. 解析所有输出:从每个阶段的输出中提取所需数据,用于下一阶段
  4. 通过TodoList自动续行:检查TodoList状态,自动执行下一个待处理阶段
  5. 跟踪进度:使用任务附加/折叠模式动态更新TodoWrite
  6. 任务附加模型:Skill执行时会将子任务附加到当前工作流。协调器自行执行这些附加任务,完成后将其折叠
  7. 渐进式阶段加载:仅在即将执行某阶段时才读取该阶段的文档
  8. 持续执行:多阶段工作流持续进行。执行完所有附加任务后,立即将其折叠并执行下一阶段

Input Processing

输入处理

Convert User Input to Structured Format:
  1. Simple Text → Structure it:
    User: "Build authentication system"
    
    Structured:
    GOAL: Build authentication system
    SCOPE: Core authentication features
    CONTEXT: New implementation
  2. Detailed Text → Extract components:
    User: "Add JWT authentication with email/password login and token refresh"
    
    Structured:
    GOAL: Implement JWT-based authentication
    SCOPE: Email/password login, token generation, token refresh endpoints
    CONTEXT: JWT token-based security, refresh token rotation
  3. File Reference (e.g.,
    requirements.md
    ) → Read and structure:
    • Read file content
    • Extract goal, scope, requirements
    • Format into structured description
将用户输入转换为结构化格式:
  1. 简单文本 → 结构化处理:
    用户: "构建认证系统"
    
    结构化结果:
    GOAL: 构建认证系统
    SCOPE: 核心认证功能
    CONTEXT: 全新实现
  2. 详细文本 → 提取组件:
    用户: "添加支持邮箱/密码登录和令牌刷新的JWT认证"
    
    结构化结果:
    GOAL: 实现基于JWT的认证
    SCOPE: 邮箱/密码登录、令牌生成、令牌刷新端点
    CONTEXT: 基于JWT令牌的安全机制、刷新令牌轮换
  3. 文件引用(例如
    requirements.md
    )→ 读取并结构化:
    • 读取文件内容
    • 提取目标、范围、需求
    • 格式化为结构化描述

Data Flow

数据流

Plan Mode

Plan模式

User Input (task description)
[Convert to Structured Format]
    ↓ Structured Description:
    ↓   GOAL: [objective]
    ↓   SCOPE: [boundaries]
    ↓   CONTEXT: [background]
Phase 1: session:start --auto "structured-description"
    ↓ Output: sessionId
    ↓ Write: planning-notes.md (User Intent section)
Phase 2: context-gather --session sessionId "structured-description"
    ↓ Input: sessionId + structured description
    ↓ Output: contextPath (context-package.json) + conflictRisk
    ↓ Update: planning-notes.md (Context Findings + Consolidated Constraints)
Phase 3: conflict-resolution [conditional: conflictRisk ≥ medium]
    ↓ Input: sessionId + contextPath + conflictRisk
    ↓ Output: Modified brainstorm artifacts
    ↓ Update: planning-notes.md (Conflict Decisions + Consolidated Constraints)
    ↓ Skip if conflictRisk is none/low → proceed directly to Phase 4
Phase 4: task-generate-agent --session sessionId
    ↓ Input: sessionId + planning-notes.md + context-package.json + brainstorm artifacts
    ↓ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md
Plan Confirmation (User Decision Gate):
    ├─ "Verify Plan Quality" (Recommended) → Route to Phase 5
    ├─ "Start Execution" → Skill(skill="workflow-execute")
    └─ "Review Status Only" → Display session status inline
Session Memory Flow: Each phase receives session ID, which provides access to:
  • Previous task summaries
  • Existing context and analysis
  • Brainstorming artifacts (potentially modified by Phase 3)
  • Session-specific configuration
用户输入(任务描述)
[转换为结构化格式]
    ↓ 结构化描述:
    ↓   GOAL: [目标]
    ↓   SCOPE: [范围]
    ↓   CONTEXT: [背景]
阶段1: session:start --auto "structured-description"
    ↓ 输出: sessionId
    ↓ 写入: planning-notes.md(用户意图部分)
阶段2: context-gather --session sessionId "structured-description"
    ↓ 输入: sessionId + 结构化描述
    ↓ 输出: contextPath(context-package.json) + conflictRisk
    ↓ 更新: planning-notes.md(上下文发现 + 合并约束)
阶段3: conflict-resolution [条件触发:conflictRisk ≥ medium]
    ↓ 输入: sessionId + contextPath + conflictRisk
    ↓ 输出: 修改后的头脑风暴工件
    ↓ 更新: planning-notes.md(冲突决策 + 合并约束)
    ↓ 若conflictRisk为none/low则跳过 → 直接进入阶段4
阶段4: task-generate-agent --session sessionId
    ↓ 输入: sessionId + planning-notes.md + context-package.json + 头脑风暴工件
    ↓ 输出: IMPL_PLAN.md、任务JSON文件、TODO_LIST.md
计划确认(用户决策节点):
    ├─ "验证计划质量"(推荐)→ 路由至阶段5
    ├─ "开始执行" → Skill(skill="workflow-execute")
    └─ "仅查看状态" → 内联显示会话状态
会话内存流:每个阶段都会接收sessionId,通过该ID可访问:
  • 历史任务摘要
  • 现有上下文和分析结果
  • 头脑风暴工件(可能已被阶段3修改)
  • 会话专属配置

Verify Mode

Verify模式

Input: --session sessionId (or auto-detect)
Phase 5: Load artifacts → Agent-driven verification → Generate report
    ↓ Output: PLAN_VERIFICATION.md with quality gate
输入: --session sessionId(或自动检测)
阶段5: 加载工件 → Agent驱动的验证 → 生成报告
    ↓ 输出: 带有质量门的PLAN_VERIFICATION.md

Replan Mode

Replan模式

Input: [--session sessionId] [task-id] "requirements"
Phase 6: Mode detection → Clarification → Impact analysis → Backup → Apply → Verify
    ↓ Output: Updated artifacts + change summary
输入: [--session sessionId] [task-id] "需求"
阶段6: 模式检测 → 澄清需求 → 影响分析 → 备份 → 应用修改 → 验证
    ↓ 输出: 更新后的工件 + 变更摘要

TodoWrite Pattern

TodoWrite模式

Core Concept: Dynamic task attachment and collapse for real-time visibility into workflow execution.
核心概念:通过动态任务附加和折叠,实时展示工作流执行进度。

Key Principles

关键原则

  1. Task Attachment (when phase executed):
    • Sub-tasks are attached to orchestrator's TodoWrite
    • Phase 2, 3: Multiple sub-tasks attached
    • Phase 1, 4: Single task (atomic)
    • First attached task marked as
      in_progress
      , others as
      pending
    • Orchestrator executes these attached tasks sequentially
  2. Task Collapse (after sub-tasks complete):
    • Applies to Phase 2, 3: Remove detailed sub-tasks from TodoWrite
    • Collapse to high-level phase summary
    • Phase 1, 4: No collapse needed (single task, just mark completed)
    • Maintains clean orchestrator-level view
  3. Continuous Execution: After completion, automatically proceed to next pending phase
Lifecycle: Initial pending → Phase executed (tasks ATTACHED) → Sub-tasks executed → Phase completed (tasks COLLAPSED for 2/3, marked completed for 1/4) → Next phase → Repeat
  1. 任务附加(阶段执行时):
    • 子任务会被附加到协调器的TodoWrite中
    • 阶段2、3:附加多个子任务
    • 阶段1、4:单个原子任务
    • 第一个附加任务标记为
      in_progress
      ,其余标记为
      pending
    • 协调器按顺序执行这些附加任务
  2. 任务折叠(子任务完成后):
    • 适用于阶段2、3:从TodoWrite中移除详细子任务
    • 折叠为高层级阶段摘要
    • 阶段1、4:无需折叠(单个任务,只需标记为已完成)
    • 保持协调器视图简洁
  3. 持续执行:完成后自动进入下一个待处理阶段
生命周期:初始待处理 → 阶段执行(任务附加)→ 子任务执行 → 阶段完成(阶段2/3的任务折叠,阶段1/4的任务标记为已完成)→ 下一阶段 → 重复

Phase 2 (Tasks Attached):

阶段2(任务附加状态):

json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "in_progress"},
  {"content": "  → Analyze codebase structure", "status": "in_progress"},
  {"content": "  → Identify integration points", "status": "pending"},
  {"content": "  → Generate context package", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "in_progress"},
  {"content": "  → Analyze codebase structure", "status": "in_progress"},
  {"content": "  → Identify integration points", "status": "pending"},
  {"content": "  → Generate context package", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]

Phase 2 (Collapsed):

阶段2(任务折叠状态):

json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]

Phase 3 (Tasks Attached, conditional):

阶段3(任务附加状态,条件触发):

json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 3: Conflict Resolution", "status": "in_progress"},
  {"content": "  → Detect conflicts with CLI analysis", "status": "in_progress"},
  {"content": "  → Present conflicts to user", "status": "pending"},
  {"content": "  → Apply resolution strategies", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
Note: See individual Phase descriptions for detailed TodoWrite Update examples.
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 3: Conflict Resolution", "status": "in_progress"},
  {"content": "  → Detect conflicts with CLI analysis", "status": "in_progress"},
  {"content": "  → Present conflicts to user", "status": "pending"},
  {"content": "  → Apply resolution strategies", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
注意:各阶段的TodoWrite更新示例请参考具体阶段描述文件。

Post-Phase Updates

阶段后更新

After each phase completes, update planning-notes.md:
  • After Phase 1: Initialize with user intent (GOAL, KEY_CONSTRAINTS)
  • After Phase 2: Add context findings (CRITICAL_FILES, ARCHITECTURE, CONFLICT_RISK, CONSTRAINTS)
  • After Phase 3: Add conflict decisions (RESOLVED, MODIFIED_ARTIFACTS, CONSTRAINTS) if executed
  • Memory State Check: After heavy phases (Phase 2-3), evaluate context window usage; if high (>120K tokens), trigger
    compact
See phase files for detailed update code.
每个阶段完成后,更新planning-notes.md:
  • 阶段1后:初始化用户意图(GOAL、KEY_CONSTRAINTS)
  • 阶段2后:添加上下文发现结果(CRITICAL_FILES、ARCHITECTURE、CONFLICT_RISK、CONSTRAINTS)
  • 阶段3后:若执行了该阶段,添加冲突决策(RESOLVED、MODIFIED_ARTIFACTS、CONSTRAINTS)
  • 内存状态检查:在资源消耗较大的阶段(阶段2-3)后,评估上下文窗口使用情况;若占用过高(>120K tokens),触发
    compact
    操作
详细更新代码请参考各阶段文件。

Error Handling

错误处理

  • Parsing Failure: If output parsing fails, retry command once, then report error
  • Validation Failure: If validation fails, report which file/data is missing
  • Command Failure: Keep phase
    in_progress
    , report error to user, do not proceed to next phase
  • Session Not Found (verify/replan): Report error with available sessions list
  • Task Not Found (replan): Report error with available tasks list
  • 解析失败:若输出解析失败,重试一次命令,然后报告错误
  • 验证失败:若验证失败,报告缺失的文件/数据
  • 命令失败:保持阶段为
    in_progress
    状态,向用户报告错误,不进入下一阶段
  • 会话未找到(验证/重规划模式):报告错误并列出可用会话
  • 任务未找到(重规划模式):报告错误并列出可用任务

Coordinator Checklist

协调器检查清单

Plan Mode

Plan模式

  • Pre-Phase: Convert user input to structured format (GOAL/SCOPE/CONTEXT)
  • Initialize TodoWrite before any command (Phase 3 added dynamically after Phase 2)
  • Execute Phase 1 immediately with structured description
  • Parse session ID from Phase 1 output, store in memory
  • Pass session ID and structured description to Phase 2 command
  • Parse context path from Phase 2 output, store in memory
  • Extract conflictRisk from context-package.json: Determine Phase 3 execution
  • If conflictRisk ≥ medium: Launch Phase 3 conflict-resolution with sessionId and contextPath
  • Wait for Phase 3 to finish executing (if executed), verify conflict-resolution.json created
  • If conflictRisk is none/low: Skip Phase 3, proceed directly to Phase 4
  • Pass session ID to Phase 4 command
  • Verify all Phase 4 outputs
  • Plan Confirmation Gate: Present user with choice (Verify → Phase 5 / Execute / Review Status)
  • If user selects Verify: Read phases/05-plan-verify.md, execute Phase 5 in-process
  • If user selects Execute: Skill(skill="workflow-execute")
  • If user selects Review: Display session status inline
  • Auto mode (workflowPreferences.autoYes): Auto-select "Verify Plan Quality", then auto-continue to execute if PROCEED
  • Update TodoWrite after each phase
  • After each phase, automatically continue to next phase based on TodoList status
  • 阶段前:将用户输入转换为结构化格式(GOAL/SCOPE/CONTEXT)
  • 在执行任何命令前初始化TodoWrite(阶段3会在阶段2后动态添加)
  • 使用结构化描述立即执行阶段1
  • 从阶段1的输出中解析sessionId,存储到内存
  • 将sessionId和结构化描述传递给阶段2的命令
  • 从阶段2的输出中解析contextPath,存储到内存
  • 从context-package.json中提取conflictRisk:决定是否执行阶段3
  • 若conflictRisk ≥ medium:启动阶段3的冲突解决流程,传入sessionId和contextPath
  • 等待阶段3执行完成(若已执行),确认conflict-resolution.json已创建
  • 若conflictRisk为none/low:跳过阶段3,直接进入阶段4
  • 将sessionId传递给阶段4的命令
  • 验证阶段4的所有输出
  • 计划确认节点:向用户提供选项(验证 → 阶段5 / 执行 / 查看状态)
  • 若用户选择验证:读取phases/05-plan-verify.md,进程内执行阶段5
  • 若用户选择执行:调用Skill(skill="workflow-execute")
  • 若用户选择查看:内联显示会话状态
  • 自动模式(workflowPreferences.autoYes):自动选择「验证计划质量」,若质量门通过则自动进入执行环节
  • 每个阶段完成后更新TodoWrite
  • 每个阶段完成后,根据TodoList状态自动进入下一阶段

Verify Mode

Verify模式

  • Detect/validate session (auto-detect from active sessions)
  • Initialize TodoWrite with single verification task
  • Execute Phase 5 verification agent
  • Present quality gate result and next step options
  • 检测/验证会话(从活跃会话中自动检测)
  • 初始化TodoWrite,添加单个验证任务
  • 执行阶段5的验证Agent
  • 呈现质量门结果和下一步选项

Replan Mode

Replan模式

  • Parse task ID from $ARGUMENTS (IMPL-N format, if present)
  • Detect operation mode (task vs session)
  • Initialize TodoWrite with replan-specific tasks
  • Execute Phase 6 through all sub-phases (clarification → impact → backup → apply → verify)
  • 从$ARGUMENTS中解析任务ID(格式为IMPL-N,若存在)
  • 检测操作模式(任务级 vs 会话级)
  • 初始化TodoWrite,添加重规划专属任务
  • 执行阶段6的所有子步骤(需求澄清 → 影响分析 → 备份 → 应用修改 → 验证)

Structure Template Reference

结构模板参考

Minimal Structure:
GOAL: [What to achieve]
SCOPE: [What's included]
CONTEXT: [Relevant info]
Detailed Structure (optional, when more context available):
GOAL: [Primary objective]
SCOPE: [Included features/components]
CONTEXT: [Existing system, constraints, dependencies]
REQUIREMENTS: [Specific technical requirements]
CONSTRAINTS: [Limitations or boundaries]
最简结构:
GOAL: [要实现的目标]
SCOPE: [包含范围]
CONTEXT: [相关信息]
详细结构(可选,上下文充足时使用):
GOAL: [核心目标]
SCOPE: [包含的功能/组件]
CONTEXT: [现有系统、约束、依赖]
REQUIREMENTS: [具体技术要求]
CONSTRAINTS: [限制条件或边界]

Related Skills

相关Skill

Prerequisite Skills:
  • /workflow:brainstorm:artifacts
    - Optional: Generate role-based analyses before planning
  • /workflow:brainstorm:synthesis
    - Optional: Refine brainstorm analyses with clarifications
Called by Plan Mode (4 phases):
  • /workflow:session:start
    - Phase 1: Create or discover workflow session
  • phases/02-context-gathering.md
    - Phase 2: Gather project context and analyze codebase (inline)
  • phases/03-conflict-resolution.md
    - Phase 3: Detect and resolve conflicts (inline, conditional)
  • /compact
    - Phase 3: Memory optimization (if context approaching limits)
  • phases/04-task-generation.md
    - Phase 4: Generate task JSON files (inline)
Follow-up Skills:
  • /workflow:plan-verify
    - Verify plan quality (can also invoke via verify mode)
  • Display session status inline - Review task breakdown and current progress
  • Skill(skill="workflow-execute")
    - Begin implementation of generated tasks (skill: workflow-execute)
  • /workflow:replan
    - Modify plan (can also invoke via replan mode)
前置Skill:
  • /workflow:brainstorm:artifacts
    - 可选:规划前生成基于角色的分析结果
  • /workflow:brainstorm:synthesis
    - 可选:通过澄清优化头脑风暴分析结果
Plan模式调用的Skill(4个阶段):
  • /workflow:session:start
    - 阶段1:创建或发现工作流会话
  • phases/02-context-gathering.md
    - 阶段2:收集项目上下文并分析代码库(内联执行)
  • phases/03-conflict-resolution.md
    - 阶段3:检测并解决冲突(内联执行,条件触发)
  • /compact
    - 阶段3:内存优化(若上下文占用接近上限)
  • phases/04-task-generation.md
    - 阶段4:生成任务JSON文件(内联执行)
后续Skill:
  • /workflow:plan-verify
    - 验证计划质量(也可通过验证模式调用)
  • 内联显示会话状态 - 查看任务分解和当前进度
  • Skill(skill="workflow-execute")
    - 开始执行生成的任务(Skill:workflow-execute)
  • /workflow:replan
    - 修改计划(也可通过重规划模式调用)