Agent skill
workflow-orchestration
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.
Install this agent skill to your Project
npx add-skill https://github.com/joaquimscosta/arkhe-claude-plugins/tree/main/plugins/core/skills/workflow-orchestration
SKILL.md
Workflow Orchestration
Guide users through structured thinking and recommend appropriate tools for complex tasks.
Quick Decision
| Situation | Recommendation |
|---|---|
| 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 impact | deep-think-partner agent |
| Simple task, clear steps | Inline 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:
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:
- Clarify scope - What exactly needs to be done?
- Identify dependencies - What must happen first?
- Plan sequence - Parallel where possible, sequential where required
- Execute - Work through each step
- Verify - Check results meet requirements
Model Tier Strategy
| Task Type | Model | Use Case |
|---|---|---|
| Gating, routing | haiku | Quick decisions, simple queries |
| Implementation | sonnet | Standard coding, documentation |
| Deep analysis | opus | Architecture, complex reasoning |
Output
When providing orchestration guidance:
## 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
- WORKFLOW.md - Detailed orchestration patterns
- EXAMPLES.md - Real-world usage scenarios
- TROUBLESHOOTING.md - Common issues and solutions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
Skill Name
What this skill does. Use when user mentions "keyword1", "keyword2", or "keyword3". Keep under 1,024 characters and include specific trigger keywords.
plugin-release-checker
skill-validator
Validate skills against Anthropic best practices for frontmatter, structure, content, file organization, hooks, MCP, and security (62 rules in 8 categories). Use when creating new skills, updating existing skills, before publishing skills, reviewing skill quality, or when user mentions "validate skill", "check skill", "skill best practices", "skill review", or "lint skill".
sync-docs
Sync official Anthropic documentation and analyze impact on project components. Runs docs/reference/update-claude-docs.sh, computes diffs, and reports impacts on the skill validator, plugins, and project documentation. Use when user mentions "sync docs", "update reference docs", "refresh docs", or "check doc changes".
research-frontmatter
Enforce standard YAML frontmatter on research documents in docs/research/. Use when creating, editing, or promoting research files, when user mentions "research metadata", "research frontmatter", or "research staleness".
deep-research
Deep research on technical topics using EXA tools with intelligent two-tier caching. Use when user asks to research a topic, investigate best practices, look up information, find patterns, or explore architectures. Also invoked by /research command. Triggers: "research", "look up", "investigate", "deep dive", "find information about", "what are best practices for", "how do others implement".
Didn't find tool you were looking for?