subagent-orchestration | claudefiles | ClaudePluginHub

Skill

Community

subagent-orchestration

From claudefiles

1

Description

This skill should be used when coordinating multiple subagents, implementing orchestrator patterns, or managing parallel agent workflows. Trigger phrases: "orchestrate agents", "coordinate subagents", "parallel agents", "multi-agent workflow", "delegate to agents", "run agents in parallel", "launch multiple agents".

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Orchestrating Subagents

Core Principles

Always suggest subagent invocation when task matches their expertise
User has final decision on invocation
Prefer multiple parallel invocations for independent tasks with strict scopes
ALWAYS define: files to modify, files NOT to touch, specific task boundaries

When to Use Parallel Invocation

Invoke multiple subagents in a single message when:

Tasks are completely independent
Each task has strict, non-overlapping scope
No task depends on another's results

Examples:

✓ "Explore authentication flow" + "Review recent auth changes" (parallel)
✗ "Explore auth flow then refactor based on findings" (sequential - second depends on first)

Scope Definition Template

When proposing subagent invocation, use this structure:

Task: [Clear, single-sentence description]

Files to modify: [Explicit list with paths]

Files NOT to touch: [Explicit exclusions - be specific]

Constraints: 
- [Business rules to follow]
- [Patterns to maintain]
- [Technical requirements]

Reference docs: [@AGENTS.md, @docs/architecture.md, etc.]

Decision Framework

Before suggesting subagents, verify:

Is the scope clearly bounded? Can you define exact files and boundaries?
Is it independent? Does it require results from another task first?
Is it delegable? Would a subagent have enough context?

If any answer is "no", handle the task directly or break it down further.

Anti-patterns to Avoid

Vague file specifications ("update related files")
Missing exclusions (failing to specify what NOT to touch)
Sequential tasks disguised as parallel (one depends on the other)
Unbounded scopes ("refactor the codebase")
Missing context references (no @file references for subagent to read)

Links

GitHub Stats

0 forks

Updated 2 hours ago

Related Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

From plugin-dev