Subagent orchestration
Skill ArcanEdge-AI/claude-code-agent-playbook/skills/subagent-orchestration
Custom instructions, subagents, skills, and reference docs for production-grade Claude Code agents.
npx -y skills add ArcanEdge-AI/claude-code-agent-playbook --skill subagent-orchestrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a coding task may benefit from Claude Code subagents for codebase exploration, review, docs research, test triage, or isolated implementation. Helps the main agent delegate bounded work and verify outputs before accepting them.
SKILL.md
2.0 KB, 375 tokens by cl100k_base, as published. Nobody here has run it
Subagent Orchestration Skill
The main agent is the senior developer and orchestrator. Subagents assist but do not own the outcome.
Use this skill when:
- the task is complex, multi-file, risky, or ambiguous
- independent read-heavy exploration would help
- review from another perspective would improve quality
- documentation or external API behavior needs verification
- logs, tests, or large files need focused analysis
- a small isolated implementation can be delegated safely
Do not use this skill when:
- the task is trivial
- one coherent design judgment is required
- requirements are materially unclear
- subagents would edit the same files
- the main agent cannot verify the result
Workflow:
- Clarify the task goal and success criteria.
- Decide which work, if any, should be delegated.
- Choose from the Claude Code roles: Read-Only Explorer, Senior Reviewer, Docs Researcher, Test Triager, and Isolated Worker.
- Right-size the model when model selection is available:
- use cheaper or faster models for bounded, low-risk, easily verifiable work
- use stronger reasoning for meaningful review, ambiguous debugging, security-sensitive work, complex test triage, and high-impact implementation
- Give each subagent a precise assignment:
- role
- goal
- context
- model / reasoning guidance
- scope
- non-goals
- permissions
- required evidence
- output format
- Wait for delegated results before accepting conclusions.
- Verify subagent claims against primary evidence.
- Inspect any changed files yourself.
- Accept, reject, or revise subagent recommendations.
- Report relevant subagent usage in the final response.
Never accept a subagent's conclusion solely because it sounds confident.
Gives 0 of the 12 instructions most agent orchestration skills give in 375 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06
- run the full test suite after integrating changesin 53 of 742, across 20 files
- reference existing artifacts by path or URLin 52 of 742, across 22 files
- dispatch one agent per independent problem domainin 50 of 742, across 17 files
- verify fixes do not conflictin 45 of 742, across 13 files
- include a suggested skills section in the documentin 45 of 742, across 15 files
- redact sensitive informationin 41 of 742, across 11 files
- save to the temporary directory of the operating systemin 39 of 742, across 9 files
- tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- spot check agent changes for systematic errorsin 34 of 742, across 7 files
- write a handoff document summarising the current conversationin 31 of 742, across 6 files
- assign each agent a specific scopein 23 of 742, across 8 files
- provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- clarify task goals and success criteria
- decide which work should be delegated
- right-size the model for the delegated work
- wait for delegated results before accepting conclusions
- verify subagent claims against primary evidence
- inspect any changed files yourself
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.