Back to Details

workflow-orchestration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Workflow Orchestration Skill

工作流编排技能

This skill provides patterns for coordinating workflow phases, managing agent handoffs, and maintaining the workflow state machine.
本技能提供了协调工作流阶段、管理Agent交接以及维护工作流状态机的模式。

Workflow State Machine

工作流状态机

Phase States

阶段状态

        ┌─────────────────────────────────────────────────┐
        │                                                 │
        v                                                 │
┌──────────┐    ┌─────────┐    ┌──────────┐    ┌────────┐ │ ┌──────────┐
│   INIT   │ -> │ DISCUSS │ -> │   PLAN   │ -> │EXECUTE │-┘>│  VERIFY  │
└──────────┘    └─────────┘    └──────────┘    └────────┘   └──────────┘
                    ^               ^              │              │
                    │               │              │              │
                    └───────────────┴──────────────┘              │
                          (on issues found)                       │
                                                                  v
                                                            ┌──────────┐
                                                            │ COMPLETE │
                                                            └──────────┘
        ┌─────────────────────────────────────────────────┐
        │                                                 │
        v                                                 │
┌──────────┐    ┌─────────┐    ┌──────────┐    ┌────────┐ │ ┌──────────┐
│   INIT   │ -> │ DISCUSS │ -> │   PLAN   │ -> │EXECUTE │-┘>│  VERIFY  │
└──────────┘    └─────────┘    └──────────┘    └────────┘   └──────────┘
                    ^               ^              │              │
                    │               │              │              │
                    └───────────────┴──────────────┘              │
                          (发现问题时)                       │
                                                                  v
                                                            ┌──────────┐
                                                            │ COMPLETE │
                                                            └──────────┘

Valid Transitions

有效转换

FromToCondition
INITDISCUSSInitialization complete
DISCUSSPLANRequirements captured
PLANEXECUTEPlan approved
EXECUTEVERIFYAll tasks complete
EXECUTEDISCUSSMajor scope change needed
EXECUTEPLANTask restructure needed
VERIFYCOMPLETESign-off received
VERIFYEXECUTEIssues need fixing
起始阶段目标阶段条件
INITDISCUSS初始化完成
DISCUSSPLAN需求已捕获
PLANEXECUTE计划已批准
EXECUTEVERIFY所有任务完成
EXECUTEDISCUSS需要进行重大范围变更
EXECUTEPLAN需要重构任务
VERIFYCOMPLETE已收到签署确认
VERIFYEXECUTE问题需要修复

Invalid Transitions

无效转换

  • INIT → PLAN (must discuss first)
  • INIT → EXECUTE (must plan first)
  • VERIFY → DISCUSS (must execute changes)
  • COMPLETE → any (workflow finished)
  • INIT → PLAN（必须先进行讨论）
  • INIT → EXECUTE（必须先制定计划）
  • VERIFY → DISCUSS（必须先执行变更）
  • COMPLETE → 任意阶段（工作流已结束）

Phase Coordination

阶段协调

Phase Entry Protocol

阶段进入协议

Before entering any phase:
markdown
1. VERIFY previous phase complete
   - Check completion criteria
   - Verify artifacts exist
   - No active blockers

2. CREATE checkpoint in ITEM-XXX.md
   - Snapshot current state
   - Record transition reason
   - Note timestamp

3. UPDATE phase status
   - Set new phase
   - Reset progress to 0%
   - Record start time

4. PREPARE phase context
   - Load relevant state files
   - Identify agents needed
   - Clear stale context
进入任何阶段之前：
markdown
1. 验证上一阶段已完成
   - 检查完成标准
   - 验证工件是否存在
   - 无活跃阻塞问题

2. 在ITEM-XXX.md中创建检查点
   - 快照当前状态
   - 记录转换原因
   - 标注时间戳

3. 更新阶段状态
   - 设置新阶段
   - 将进度重置为0%
   - 记录开始时间

4. 准备阶段上下文
   - 加载相关状态文件
   - 确定所需的Agent
   - 清除过期上下文

Phase Exit Protocol

阶段退出协议

Before exiting any phase:
markdown
1. VERIFY completion criteria
   - Phase-specific requirements met
   - Artifacts created
   - No pending decisions

2. CREATE phase summary
   - What was accomplished
   - Decisions made
   - Artifacts produced

3. HANDOFF to next phase
   - What next phase needs to know
   - Key context to carry forward
   - Warnings or considerations
退出任何阶段之前：
markdown
1. 验证完成标准
   - 满足阶段特定要求
   - 已创建工件
   - 无待决策事项

2. 创建阶段总结
   - 已完成的工作内容
   - 做出的决策
   - 生成的工件

3. 交接至下一阶段
   - 下一阶段需要了解的信息
   - 需要延续的关键上下文
   - 注意事项或警告

Agent Handoff Protocols

Agent交接协议

Spawning an Agent

生成Agent

markdown
undefined
markdown
undefined

Agent Spawn: [agent-name]

Agent生成: [agent-name]

Purpose: [Clear objective]
Context provided:
  • Phase: [current phase]
  • Task: [specific task if applicable]
  • Key decisions: [relevant decisions]
  • Files: [files to read]
Expected deliverable:
  • [What agent should produce]
  • [Format expected]
Constraints:
  • [Time/scope limits]
  • [Must follow conventions]
  • [Report blockers immediately]
undefined
目的: [明确目标]
提供的上下文:
  • 阶段: [当前阶段]
  • 任务: [适用的特定任务]
  • 关键决策: [相关决策]
  • 文件: [需要读取的文件]
预期交付物:
  • [Agent应生成的内容]
  • [预期格式]
约束条件:
  • [时间/范围限制]
  • [必须遵循的规范]
  • [立即报告阻塞问题]
undefined

Receiving Agent Results

接收Agent结果

markdown
undefined
markdown
undefined

Agent Result: [agent-name]

Agent结果: [agent-name]

Status: [SUCCESS/PARTIAL/FAILED]
Deliverables:
  • [What was produced]
  • [Where it's stored]
Key findings:
  • [Important discovery]
  • [Important discovery]
Issues encountered:
  • [Issue if any]
Next recommended action:
  • [What to do next]
undefined
状态: [成功/部分完成/失败]
交付物:
  • [已生成的内容]
  • [存储位置]
关键发现:
  • [重要发现]
  • [重要发现]
遇到的问题:
  • [存在的问题（如有）]
建议的下一步操作:
  • [后续应执行的操作]
undefined

Multi-Agent Coordination

多Agent协调

When multiple agents needed:
markdown
undefined
当需要多个Agent时：
markdown
undefined

Coordination Plan

协调计划

Agents involved:
Sequence: A -> B (B depends on A's output)
Handoff points:
  • A completes: [deliverable] -> B starts
  • B completes: [deliverable] -> next phase
Fallback:
  • If A fails: [contingency]
  • If B fails: [contingency]
undefined
涉及的Agent:
顺序: A -> B（B依赖A的输出）
交接点:
  • A完成: [交付物] -> B启动
  • B完成: [交付物] -> 下一阶段
** fallback方案**:
  • 如果A失败: [应急方案]
  • 如果B失败: [应急方案]
undefined

Blocker Management

阻塞问题管理

Blocker Detection

阻塞问题检测

Watch for:
  • Explicit blockers from agents
  • Missing prerequisites
  • User unavailability
  • Technical failures
  • Conflicts requiring resolution
需要关注：
  • Agent明确上报的阻塞问题
  • 缺失的前置条件
  • 用户不可用
  • 技术故障
  • 需要解决的冲突

Blocker Response

阻塞问题响应

markdown
undefined
markdown
undefined

Blocker Detected

检测到阻塞问题

Type: [Technical/Decision/External/Conflict] Phase: [current phase] Impact: [what's blocked]
Options:
  1. Resolve blocker directly
  2. Work around blocker
  3. Pause workflow
  4. Escalate to user
Recommended: [option]
undefined
类型: [技术/决策/外部/冲突] 阶段: [当前阶段] 影响: [被阻塞的内容]
可选方案:
  1. 直接解决阻塞问题
  2. 绕过阻塞问题
  3. 暂停工作流
  4. 上报给用户
推荐方案: [选项]
undefined

Blocker Resolution Tracking

阻塞问题解决跟踪

In ITEM-XXX.md:
markdown
undefined
在ITEM-XXX.md中：
markdown
undefined

BLOCKER-XXX: [Title]

BLOCKER-XXX: [标题]

Status: ACTIVE -> RESOLVED Detected: [timestamp] Resolved: [timestamp] Resolution: [what was done] Impact on workflow: [any changes made]
undefined
状态: 活跃 -> 已解决 检测时间: [时间戳] 解决时间: [时间戳] 解决方式: [执行的操作] 对工作流的影响: [做出的任何变更]
undefined

Progress Tracking

进度跟踪

Phase Progress Calculation

阶段进度计算

PhaseProgress Based On
INITSteps completed / total steps
DISCUSSAreas explored / total areas
PLANTasks defined / estimated total
EXECUTETasks completed / total tasks
VERIFYChecks passed / total checks
阶段进度计算依据
INIT已完成步骤数 / 总步骤数
DISCUSS已探索领域数 / 总领域数
PLAN已定义任务数 / 预估总任务数
EXECUTE已完成任务数 / 总任务数
VERIFY通过检查数 / 总检查数

Progress Reporting

进度报告

markdown
undefined
markdown
undefined

Workflow Progress

工作流进度

Overall: [X]% Phase: [current phase] at [Y]%
Phase breakdown:
  • INIT: 100%
  • DISCUSS: 100%
  • PLAN: 75%
  • EXECUTE: 0%
  • VERIFY: 0%
Blockers: [count] Next milestone: [description]
undefined
整体进度: [X]% 当前阶段: [当前阶段]，进度[Y]%
阶段细分:
  • INIT: 100%
  • DISCUSS: 100%
  • PLAN: 75%
  • EXECUTE: 0%
  • VERIFY: 0%
阻塞问题数量: [数量] 下一个里程碑: [描述]
undefined

Rollback and Recovery

回滚与恢复

Phase Rollback

阶段回滚

When needing to return to earlier phase:
markdown
undefined
当需要返回至更早阶段时：
markdown
undefined

Phase Rollback

阶段回滚

From: [current phase] To: [target phase] Reason: [why rolling back]
Actions:
  1. Save current state as checkpoint
  2. Preserve completed work
  3. Update phase status
  4. Clear invalid artifacts (if any)
  5. Resume from target phase
undefined
起始阶段: [当前阶段] 目标阶段: [目标阶段] 原因: [回滚原因]
操作:
  1. 将当前状态保存为检查点
  2. 保留已完成的工作
  3. 更新阶段状态
  4. 清除无效工件（如有）
  5. 从目标阶段恢复执行
undefined

Recovery from Failure

故障恢复

markdown
undefined
markdown
undefined

Workflow Recovery

工作流恢复

Failure point: [where it failed] Error: [what happened]
Recovery options:
  1. Retry from checkpoint
  2. Skip failed item
  3. Manual intervention
  4. Abort with state preserved
State preserved at: .flow/FLOW.md and .flow/items/ITEM-XXX.md Resume command: /flow-workflow:go
undefined
故障点: [故障发生位置] 错误信息: [发生的问题]
恢复选项:
  1. 从检查点重试
  2. 跳过失败项
  3. 手动干预
  4. 保留状态并终止
保留的状态位置: .flow/FLOW.md 和 .flow/items/ITEM-XXX.md 恢复命令: /flow-workflow:go
undefined

Quick Mode Orchestration

快速模式编排

For 
/flow-workflow:quick
:
markdown
undefined
对于
/flow-workflow:quick
命令：
markdown
undefined

Quick Mode Flow

快速模式流程

Simplified phases: ASSESS -> CLARIFY -> IMPLEMENT -> VERIFY
Shortcuts taken:
  • No FLOW.md or ITEM-XXX.md files created
  • No detailed requirements gathering
  • Direct execution
  • Brief verification
Escalation trigger: If complexity exceeds quick mode, escalate to full workflow with /flow-workflow:start
undefined
简化阶段: 评估 -> 澄清 -> 实施 -> 验证
采用的快捷方式:
  • 不创建FLOW.md或ITEM-XXX.md文件
  • 不进行详细的需求收集
  • 直接执行
  • 简短验证
升级触发条件: 如果复杂度超出快速模式范围，使用/flow-workflow:start升级至完整工作流
undefined

Integration Points

集成点

With State Management

与状态管理的集成

  • Update FLOW.md and ITEM-XXX.md on every transition
  • Create checkpoints in ITEM-XXX.md at key points
  • Maintain phase history in ITEM-XXX.md
  • 在每次转换时更新FLOW.md和ITEM-XXX.md
  • 在关键节点的ITEM-XXX.md中创建检查点
  • 在ITEM-XXX.md中维护阶段历史记录

With Capability Discovery

与能力发现的集成

  • Route to appropriate agents based on FLOW.md cache
  • Announce delegation decisions with reasoning
  • Fallback to defaults when no match
  • Log capability gaps in FLOW.md
  • 根据FLOW.md缓存路由至合适的Agent
  • 附带决策依据宣布委托决定
  • 无匹配项时回退至默认设置
  • 在FLOW.md中记录能力缺口

With Conflict Detection

与冲突检测的集成

  • Block transitions on active conflicts
  • Require resolution before proceeding
  • Document resolved conflicts in ITEM-XXX.md
  • 存在活跃冲突时阻止转换
  • 要求解决冲突后再继续
  • 在ITEM-XXX.md中记录已解决的冲突

With Context Engineering

与上下文工程的集成

  • Fresh context per task
  • Coordinator stays under 40%
  • Spawn fresh agents when approaching threshold
  • 为每个任务提供全新上下文
  • 协调器占用率保持在40%以下
  • 接近阈值时生成新的Agent