agent-patterns

Coordinate parallel agents using SPAWN REQUEST blocks to define which agents to activate. The orchestrator spawns multiple specialized agents simultaneously, manages their execution flow, and collects standardized reports from each agent, enabling scalable parallel workflows across backend, frontend, QA, and testing tasks.

SPAWN REQUEST is a structured block format that specifies which agents to activate in parallel. List agent names under a SPAWN REQUEST header, and the orchestrator parses and executes them concurrently. This format ensures consistent agent spawning, clear coordination rules, and structured inter-agent communication.

Agents communicate through file-based coordination with structured messages. The orchestrator enforces strict rules: only it spawns agents, agents produce standardized reports, and all communication follows a defined message structure. This ensures reliable coordination and conformity across parallel workflows.

Yes, orchestrate sprint workflows across backend, frontend, QA, and UI testing by spawning specialized agents for each domain. Each agent produces a standardized report, and the orchestrator aggregates results, enabling end-to-end sprint coordination with clear role separation and parallel execution.

Only the orchestrator spawns agents; agents cannot spawn other agents. All agents must produce reports conforming to a standardized structure. Coordination relies on file-based messaging, so ensure your environment supports persistent file I/O and structured message passing between processes.

Agent reports must follow a standardized structure defined by the orchestration pattern. The skill enforces conformity checks, validating each agent's output against the schema before aggregation. This ensures consistent report structure across all agents and reliable downstream processing.