orch-delegation
Domain: orch · Model class: strong
Description
Section titled “Description”Use this skill when the user wants to work on Defining how and when tasks are delegated to specialist subagents. Triggers include “how should I delegate tasks to subagents”, “delegation strategy for my agent system”, “route by capability boundary”. Do NOT use when design the overall multi-agent architecture (use core-multi-agent-design).
Purpose
Section titled “Purpose”Defining how and when tasks are delegated to specialist subagents. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.
Trigger Phrases
Section titled “Trigger Phrases”- “how should I delegate tasks to subagents”
- “delegation strategy for my agent system”
- “route by capability boundary”
- “subagent task assignment”
Anti-Triggers
Section titled “Anti-Triggers”- design the overall multi-agent architecture (use core-multi-agent-design)
- set up the lead agent (use core-agent-orchestrator)
Intake Questions
Section titled “Intake Questions”- What is the user’s goal and current state?
- What constraints (time, team, compliance) apply?
- Are there existing artifacts (specs, code, benchmarks) to reference?
Output Contract
Section titled “Output Contract”- orchestration topology
- agent responsibility map
- control-loop or validation contract
- handoff guidance
Related Skills
Section titled “Related Skills”orch-agent-orchestrator · orch-multi-agent · gov-workflow-compliance