Repository navigation
Decide: add a "Squad as a software factory" scenario page? #2430
Description
@bradygaster, this one is your call.
Context
A user asked whether Squad can run a "software factory" on GitHub. Their reference was Warp Factories, where teams of cloud agents turn issues and tickets into reviewed pull requests and people approve specs and merges.
Squad already has most of the pieces, but no docs page presents them as one flow:
| Factory piece | Squad today |
|---|---|
| The factory is defined as code and changed through PRs | .squad/ (team, routing, charters, skills); the squad-bootstrap workflow opens the cast PR |
| Cloud agents turn issues into PRs | gh-aw workflows (squad-implement-worker and the Squad slash commands) and the Copilot coding agent |
| Agents run on your own machines | squad watch --execute (Ralph), fleet dispatch, multi-machine watch, KEDA scaling |
| People approve at checkpoints | squad-review (an independent reviewer), the cast PR, branch protection |
| The factory improves itself | squad-retro proposes changes; after a person approves one, squad-improvement-worker opens it as a draft PR |
| Work arrives from many tools | GitHub issues (watch also reads Azure DevOps); two-way Teams chat through the SDK; notifications to Slack, Discord and webhooks |
Proposal
Add a scenario page that walks through this flow end to end. docs-devrel would own it.
Decision needed
- Should we add the page?
- If so, should it use the "factory" framing and compare Squad with Warp Factories, or describe Squad's flow on its own terms?
Reacted by Brady Gaster
Activity
bradygaster commentedon Nov 9, 2026
Love the idea, just remember to work in the gh-aw use-cases.