Menu
">"
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CleanExpo/NodeJS-Starter-V1 --skill delegation-plannerThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Route complex requests to the right specialist agent or chain of agents. This skill acts as the central brain of an agent swarm โ it analyses what the user needs, determines which specialist domain(s) are required, and coordinates parallel or sequential agent execution. Use this skill when a request spans multiple domains (e.g., "research competitors and create a pitch deck"), when you need to decide which specialist should handle an ambiguous request, or when a task requires a multi-step pipeline across different skills. Triggers on: multi-step requests, cross-domain tasks, "coordinate", "plan this out", "I need help with multiple things", or any complex request that touches more than one specialist area. Also triggers when the user seems unsure which tool or approach to use.
>-
Hybrid DAG execution primitive combining deterministic and agentic nodes with hard iteration caps
Based on SOC occupation classification
Showing SKILL.md
| id | delegation-planner |
| name | delegation-planner |
| type | Capability Uplift |
| version | 1.0.0 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| triggers | ["who should do this","which agent handles","delegate this","plan delegation","assign tasks","who handles","which specialist","route this task","assign work"] |
| description | > |
| context | fork |
Purpose: Route every task to the correct agent layer before execution begins. Wrong routing wastes context budget and produces inferior output.
Use this skill when:
Route here when:
Do NOT route here:
Route here when:
Do NOT route here:
Route to Senior Engineering Agent when:
Route to Senior UI/UX Agent when:
Route to Senior QA / Production Agent when:
Route to Senior LMS Content Agent when:
Route to Senior Growth / Marketing Agent when:
Route here when:
Do NOT route here:
Ask: What kind of work is this?
If the task touches multiple domains (e.g., "add a feature with API + UI + tests"):
Produce the delegation plan table.
DELEGATION PLAN
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Task: [original task description]
Decomposed: [yes / no]
ROUTING
โโโโโโโโโโโโโโโโโ
| # | Sub-task | Agent | Layer | Evidence Required | Gate |
|---|---------|-------|-------|------------------|------|
| 1 | [task] | [agent] | [1-4] | [what to return] | [gate condition] |
| 2 | [task] | [agent] | [1-4] | [what to return] | [gate condition โ depends on #1] |
...
DEPENDENCY ORDER
โโโโโโโโโโโโโโโโโ
[If tasks have dependencies: show order and gate conditions]
Step 1: Task #[N] must complete before Task #[N+1] begins
Gate: [exact condition that unlocks next step]
CONTEXT BUDGET
โโโโโโโโโโโโโโโโโ
Orchestrator: [estimated tokens for coordination]
Each specialist: [estimated tokens per agent]
Total estimate: [rough total]
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Before finalising delegation plan:
| Failure | Recovery |
|---|---|
| Task is too vague to route | Ask: "What does success look like?" โ activate outcome-translator |
| Task spans all 4 layers | Decompose into phases, route each phase separately |
| Wrong agent assigned (discovered mid-task) | Re-route immediately, don't continue in wrong layer |
| Sub-agent scope creeps to architectural decision | Pause sub-agent, escalate to orchestrator |
Task: "Add a protected dashboard page with user stats"
Delegation Plan:
| # | Sub-task | Agent | Layer | Evidence Required |
|---|---|---|---|---|
| 1 | API endpoint: GET /api/user/stats | Senior Engineering | 3A | curl output + type-check |
| 2 | Dashboard page component | Senior UI/UX | 3B | Screenshot + 0 TS errors |
| 3 | Auth middleware check | Senior Engineering | 3A | curl 401 without JWT |
| 4 | E2E test for dashboard | Senior QA | 3C | Playwright test output |
Dependency order: 1 โ 3 โ 2 โ 4
Task: "Add dashboard" Response: "Sure, I'll add the dashboard." โ No routing, no decomposition, no evidence plan.