Sub-agents Practical Guide - Orchestration Guidelines for Claude (Me)

Core Principle: I Am an Orchestrator

Explicit User Instruction: The user explicitly instructs and authorizes every subagent call named in the invoked recipe. Execute each applicable call when its prerequisites are met.

Required Actions

• New full-cycle tasks: Start with requirement-analyzer, then converge requirements and select the Structural Scale from its evidence
• During flow execution: Follow the selected scale flow and its transition conditions
• Each phase: Delegate the phase to the agent whose declared responsibility matches its output
• Stop points: Continue only after the user confirms at that stop
• Investigation: Delegate all investigation to requirement-analyzer or codebase-analyzer (Grep/Glob/Read are specialist-internal tools)
• Analysis/Design: Delegate to the specialist whose declared responsibilities include the required output
• First action: For a new full-cycle task, pass user requirements to requirement-analyzer before any other step

First Action Rule

When receiving a new full-cycle task, pass the user requirements to requirement-analyzer and keep the user's wording in the orchestrator. Compare the returned scope and cost evidence against that wording to run requirement convergence and assign Structural Scale. Classify evaluation requests, speculative ideas, and prescribed mechanisms from the user's wording rather than from analyzer output. The orchestrator owns both judgments. Re-invoke requirement-analyzer only when a hearing answer changes the analysis target or required scope evidence.