subagents-orchestration-guide

Coordinate subagents through requirement analysis, scale determination, and approval-gated execution flows.

225|24|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/shinpr/ai-coding-project-boilerplate --skill subagents-orchestration-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagents-orchestration-guide
Source: https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-ja/subagents-orchestration-guide
Command: npx skills add https://github.com/shinpr/ai-coding-project-boilerplate --skill subagents-orchestration-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates coordination overhead by intelligently managing subagent workflows, determining scale, and handling autonomous execution.

Core Features & Use Cases

  • Workflow Management: Coordinate multiple subagents through implementation phases.
  • Autonomous Execution: Delegate tasks to specialized agents with proper approval workflows.

Quick Start

Use this Skill to coordinate subagents for a large-scale feature implementation.

Core Features & Use Cases

  • Scale-Based Execution: Automatically determine appropriate document requirements and stop points based on task complexity.

Quick Start

Orchestrate the implementation of a new authentication system using requirement-analyzer, technical-designer, and task-executor subagents.

Frequently Asked Questions about subagents-orchestration-guide

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

FAQPage Schema
How do I orchestrate multiple subagents to handle complex workflow automation tasks?

Orchestrate subagents by using a requirement-analyzer to assess task scope, then route work to specialized subagents based on complexity scale. The orchestrator coordinates all execution phases, enforces approval checkpoints, and prevents direct subagent-to-subagent communication, ensuring structured delegation across documentation, design, and testing deliverables.

When should I use subagent orchestration instead of running tasks sequentially?

Use orchestration for multi-phase implementations requiring autonomous execution with human approval gates—such as large-scale feature rollouts, authentication system redesigns, or projects generating PRDs, ADRs, and test plans. Scale-based delegation automatically determines document requirements and stop points, eliminating manual coordination overhead.

Can I automate requirement analysis and task delegation across multiple specialized agents?

Yes. Subagent orchestration automates requirement analysis, scale determination, and task delegation to specialized agents like technical designers and task executors. The system enforces approval workflows between phases, ensuring human oversight while removing coordination friction in multi-agent implementation flows.

What types of deliverables can I generate through coordinated subagent workflows?

Generate PRDs, architecture decision records (ADRs), design documentation, work plans, and test skeletons through coordinated subagent execution. The orchestrator routes each deliverable phase to appropriate agents based on task complexity, with built-in approval checkpoints before progressing to downstream work.

How does scale-driven delegation determine which subagents execute each workflow phase?

Scale-driven delegation analyzes task complexity and automatically selects appropriate subagents and document requirements. The orchestrator maintains a centralized routing layer that prevents agents from communicating directly, ensuring all decisions flow through the orchestrator for consistent, auditable task progression.

What prevents coordination failures when managing autonomous subagent execution?

The orchestration framework enforces stop points for user approval between phases, maintains a centralized coordinator that prevents subagent-to-subagent calls, and uses requirement analysis to set proper scale expectations. These safeguards ensure autonomous execution remains auditable and user-controlled.