Swarm Supervisor FAQs

Question 1

What happens if a worker task gets stuck?

Accepted Answer

The system includes 'stale-check' lifecycle hooks that can be triggered via cron or manual commands to identify and reset tasks that have exceeded their processing threshold.

Question 2

Can this skill handle PR merges automatically?

Accepted Answer

Yes, it integrates with a GitHub-native PR review pipeline that triages bot comments and can trigger automated merges once human approval or specific CI checks are met.

Question 3

Do I need to monitor the workers while they are running?

Accepted Answer

No, the Swarm Supervisor follows a 'dispatch and walk away' philosophy. Once tasks are dispatched to the swarm, the supervisor's role ends until the resulting pull requests arrive on GitHub.

Question 4

How does the human approval gate work?

Accepted Answer

Before tasks are dispatched, they are presented for human review. Users can approve, request changes, or backburner tasks, ensuring that AI agents only work on correctly decomposed and validated subtasks.

Question 5

What is a 'polecat' worker in this context?

Accepted Answer

A polecat is an autonomous worker agent that claims specific tasks, performs the coding work in an isolated git worktree, and submits a pull request for review without requiring active supervision.

Swarm Supervisor

Características Principales

Casos de Uso

Swarm Supervisor

Características Principales

Casos de Uso