sft-coordination-patterns

The main multi-agent coordination patterns are orchestrator-subagent, generator-verifier, agent teams, message bus, and shared state. Each provides a distinct structural template for routing tasks, managing data flows, and handling termination conditions across multiple agents.

To choose the right coordination pattern, evaluate explicit selection criteria against your workflow requirements. Compare the scale, task dependency, and verification needs of your workflow against the reference guidance to identify whether an orchestrator-subagent or shared state model fits best.

Use a generator-verifier pattern when your workflow requires explicit output validation and quality gating before proceeding. An orchestrator-subagent model is better suited for dynamic task decomposition and parallel execution where strict sequential verification is not the primary constraint.

Document coordination contracts and termination conditions by applying the provided template guidance and phase maps. This structures the prompts, tasks, and data flow boundaries that define when and how agent teams safely conclude their interactions.

Yes, these coordination templates are explicitly applicable to the design and planning phases of new skills. They provide reference material and decision guidance to structure prompts and coordination artifacts before implementation begins.