subagent-orchestration

Coordinate multiple subagents with isolated context and two-stage reviews.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill subagent-orchestration-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-orchestration
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/subagent-orchestration
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill subagent-orchestration-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fresh subagents isolated per major task to prevent stale context and improve task quality in complex workflows.

Core Features & Use Cases

  • Fresh subagent per major task to ensure specialization and isolation.
  • Explicit handoff protocols for clear context transfer between tasks.
  • Parallel execution of independent tasks with two-stage reviews to guarantee quality.

Quick Start

Outline a plan that assigns each major task to a fresh subagent and specifies explicit handoffs.

Frequently Asked Questions about subagent-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent stale context when coordinating multiple subagents for complex tasks?

To prevent stale context during multi-agent orchestration, use fresh subagents isolated per major task. This approach enforces explicit handoffs and strict review gates to maintain specialization and ensure task quality.

What is the best way to structure parallel execution with independent subagents?

The best way to structure parallel execution is assigning each independent task to a fresh subagent with explicit handoff protocols. This pattern applies two-stage reviews to guarantee quality across isolated contexts.

How does a two-stage review work in a multi-agent orchestration workflow?

A two-stage review in multi-agent orchestration works by enforcing strict review gates after parallel execution. Fresh subagents complete isolated tasks and pass explicit handoffs through these quality checks before final output.

When should I use isolated context subagents for task handoffs?

You should use isolated context subagents for task handoffs when your workflow splits into parallel, independent tasks. This prevents stale context contamination and ensures each specialized subagent operates cleanly.

Do I need specific dependencies to run parallel-execution subagent orchestration?

No specific dependencies are required to run parallel-execution subagent orchestration. You can outline a plan assigning tasks to fresh subagents and specifying explicit handoffs to start the workflow immediately.

What are the limitations of using fresh subagents per task for complex workflows?

The limitation of using fresh subagents per task is the overhead from strict review gates and explicit handoffs. This orchestration pattern suits independent parallel tasks but may add complexity for simple sequential workflows.