Swarm Supervisor FAQs

Question 1

How are task states managed during the swarm?

Accepted Answer

Task states (create, update, complete) are managed through MCP tools, while the final completion is triggered automatically when a PR is merged into the main branch.

Question 2

What is the 'fire and forget' philosophy in Swarm Supervisor?

Accepted Answer

The supervisor dispatches tasks to workers and then stops active monitoring, relying on GitHub Actions and the PR pipeline to handle the results autonomously once work is pushed.

Question 3

Can I use different types of workers with this skill?

Accepted Answer

Yes, Swarm Supervisor supports various workers like Polecat and Jules, selecting the appropriate runner based on task complexity and repository configurations defined in WORKERS.md.

Question 4

How does it handle complex, multi-faceted tasks?

Accepted Answer

It employs a decomposition phase where a large task is broken down into smaller, PR-sized subtasks. These are then reviewed by multiple agents before being approved for parallel dispatch.

Question 5

Does Swarm Supervisor require manual PR merging?

Accepted Answer

While it includes human approval gates for task starting, the PR stage is designed for automation via a specialized review pipeline and GitHub auto-merge features.

Swarm Supervisor

Key Features

Use Cases

Swarm Supervisor

Key Features

Use Cases