Goal swarm
Use parallel agents to complete one parent goal. Follow /goal-bee for the parent goal. Each child gets one bounded goal.
Require both an explicit user request to create or use a goal and authority to
delegate from the user, applicable instructions, or a parent skill. An ordinary
task request does not request a goal. For delegation without a goal, read
agent routing without opening a goal.
Steps
Open the parent goal.
Keep it active until you have added every accepted child result and the parent checks pass.
Split the work into independent shards using references/shard-types.md.
Give each shard one owner, one result, and work that does not overlap another shard. Keep work with the parent when another agent would wait on a dependency, edit the same files, or save little time.
Give each child one /goal-bee request.
Write each request so the child needs no extra context. State the result, proof, owned work, inputs, limits, checks, and return form. Name shared files and paths the child must leave alone.
Read agent routing to choose a role and apply
its model, effort, and context settings. Keep child goals within the parent
goal the user requested.
Start the ready shards.
Start ready shards within the configured concurrency limit. Wait to start
work whose inputs are missing. The parent may join finished work or take a
separate task that does not conflict with a child.
Review every child result.
Read the evidence, then accept the result, reject it with a reason, send back a narrower request, finish it with the parent, or record its blocker. Make this choice for every child before you prepare the report.
Check and close the parent.
For meaningful code changes, run /review-fix-loop on the complete integrated
diff. Child acceptance does not replace that review. Reuse a completed review
only while its scope and evidence still match the final change.
Add the accepted work and run the parent checks. Close it only when every required check passes.
Report
Name the parent goal and state. List the agents, their roles and requested
settings, their work, the choice made for each result, the checks run, and known
risks. Distinguish confirmed settings from unverified requests.
1---2name: goal-swarm3description: Split work across agents when the user explicitly requests goal-backed work and the user, applicable instructions, or a parent skill requests delegation.4---56# Goal swarm78Use parallel agents to complete one parent goal. Follow `/goal-bee` for the parent goal. Each child gets one bounded goal.910Require both an explicit user request to create or use a goal and authority to11delegate from the user, applicable instructions, or a parent skill. An ordinary12task request does not request a goal. For delegation without a goal, read13[agent routing](references/agent-routing.md) without opening a goal.1415## Steps16171. Open the parent goal.1819 Keep it active until you have added every accepted child result and the parent checks pass.20212. Split the work into independent shards using `references/shard-types.md`.2223 Give each shard one owner, one result, and work that does not overlap another shard. Keep work with the parent when another agent would wait on a dependency, edit the same files, or save little time.24253. Give each child one `/goal-bee` request.2627 Write each request so the child needs no extra context. State the result, proof, owned work, inputs, limits, checks, and return form. Name shared files and paths the child must leave alone.2829 Read [agent routing](references/agent-routing.md) to choose a role and apply30 its model, effort, and context settings. Keep child goals within the parent31 goal the user requested.32334. Start the ready shards.3435 Start ready shards within the configured concurrency limit. Wait to start36 work whose inputs are missing. The parent may join finished work or take a37 separate task that does not conflict with a child.38395. Review every child result.4041 Read the evidence, then accept the result, reject it with a reason, send back a narrower request, finish it with the parent, or record its blocker. Make this choice for every child before you prepare the report.42436. Check and close the parent.4445 For meaningful code changes, run `/review-fix-loop` on the complete integrated46 diff. Child acceptance does not replace that review. Reuse a completed review47 only while its scope and evidence still match the final change.4849 Add the accepted work and run the parent checks. Close it only when every required check passes.5051## Report5253Name the parent goal and state. List the agents, their roles and requested54settings, their work, the choice made for each result, the checks run, and known55risks. Distinguish confirmed settings from unverified requests.