AgentSkillsCN

workflow-orchestration

协调复杂任务的结构化思维与多代理并行执行。当处理多步骤项目、规划并行工作、拆解复杂问题、协调专业任务、面对架构决策，或用户提到“工作流”、“编排”、“多步骤”、“协调”、“并行执行”、“结构化思维”、“拆解这个”、“规划这个”、“我该如何着手”或需要帮助规划复杂实施时，就使用此技能。

SKILL.md
--- frontmatter
name: workflow-orchestration
description: >
  Coordinate structured thinking and multi-agent parallel execution for complex tasks.
  Use when tackling multi-step projects, planning parallel work, breaking down complex
  problems, coordinating specialist tasks, facing architectural decisions, or when user
  mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution",
  "structured thinking", "break this down", "plan this out", "how should I approach",
  or needs help planning complex implementations.

Workflow Orchestration

Guide users through structured thinking and recommend appropriate tools for complex tasks.

Quick Decision

SituationRecommendation
Multi-step project, full SDLC/core:develop command
Plan only, implement later/core:develop --plan-only
Resume existing plan/core:develop @path/to/plan.md
Single complex problem needing deep analysis/think command
Security-sensitive or high-stakes work/core:develop --validate
Strategic decision with long-term impactdeep-think-partner agent
Simple task, clear stepsInline guidance (no command needed)

When to Orchestrate

Detect these signals for structured thinking:

Keyword triggers:

  • •"workflow", "orchestration", "coordinate", "parallel"
  • •"multi-step", "sequential", "dependencies"
  • •"break down", "plan this out", "how should I approach"

Context triggers:

  • •Architectural decisions affecting multiple components
  • •Multi-file changes requiring coordination
  • •Problems with unclear scope needing discovery
  • •Tasks that benefit from specialist agents

Orchestration Pattern

When structured approach is needed:

code
1. GATE     → Is the request clear and actionable?
2. CONTEXT  → What files/patterns are relevant?
3. PLAN     → What tasks? Parallel vs sequential?
4. EXECUTE  → Deploy specialists, maximize parallelism
5. VALIDATE → Confidence scoring (if needed)
6. REPORT   → Summary with next steps

Command Reference

/core:develop <request> [flags]

Unified SDLC command with 6-phase pipeline and multi-agent orchestration.

Flags:

  • •--plan-only - Stop after Phase 2 (save plan, don't implement)
  • •--validate - Enable deep validation with opus agent
  • •--phase=N - Execute specific phase only
  • •--auto - Autonomous mode (no checkpoints)

Best for: Feature implementations, refactoring projects, any multi-step development task.

Resume mode: /core:develop @path/to/plan.md loads existing plan and continues.

/think [problem]

Invoke deep-think-partner for collaborative reasoning.

Best for: Single complex problems, decision analysis, reasoning validation, architectural decisions.

Inline Guidance

For simpler tasks, provide structured thinking directly:

  1. •Clarify scope - What exactly needs to be done?
  2. •Identify dependencies - What must happen first?
  3. •Plan sequence - Parallel where possible, sequential where required
  4. •Execute - Work through each step
  5. •Verify - Check results meet requirements

Model Tier Strategy

Task TypeModelUse Case
Gating, routinghaikuQuick decisions, simple queries
ImplementationsonnetStandard coding, documentation
Deep analysisopusArchitecture, complex reasoning

Output

When providing orchestration guidance:

markdown
## Recommended Approach

**Complexity:** [Low | Medium | High]
**Suggested tool:** [command or inline]

### Why
[Brief explanation of why this approach fits]

### Steps
1. [First step]
2. [Second step]
...

Additional Resources