Subagent Orchestration Guide FAQs

Question 1

How does the skill handle requirement changes?

Accepted Answer

If new features, constraints, or technical changes are detected during execution, the orchestrator stops the current flow and restarts from the requirement-analyzer to integrate the new information into the project scope.

Question 2

Does this skill work autonomously?

Accepted Answer

Yes, once a work plan is batch-approved by the user, the skill enters 'Autonomous Execution Mode' where it manages task decomposition and implementation without further stops until completion or escalation.

Question 3

How are subagents actually invoked?

Accepted Answer

Subagents are called using a standardized Task tool with specific JSON parameters, including the agent type, a concise description, and detailed instructions or prompts for the sub-task.

Question 4

What is the primary role of the Orchestrator?

Accepted Answer

The orchestrator acts as a conductor, directing specialized subagents to perform tasks like analysis, design, and coding without writing the code or documents directly, ensuring a clean separation of concerns.

Question 5

What are 'Stop Points' in this workflow?

Accepted Answer

Stop points are mandatory pauses where the orchestrator uses the AskUserQuestion tool to seek approval for critical documents like PRDs, ADRs, and Work Plans before proceeding to the next phase.

Subagent Orchestration Guide

Subagent Orchestration Guide

Key Features

Use Cases

Key Features

Use Cases