Repository navigation
Squad management paradigms #211
Description
There are several levels of squad management that need to be added to the docs:
- GH org squad
- Personal squad
- Repo squad
- Local machine squad
There will be orgs and repos where .Squad will not be allowed to be checked in --- like MicrosoftDocs. However, the Squad should still be able to function and retain history without the requirement to be checked into an org or repo. An option to check into a personal repo or remain on the local machine would be helpful.
The docs should help the developer (and the org) reason through the best place to retain squad files. The doc should also figure how to borrow squad members, deal with inter-squad relationships such as duplicate personnel, and hiring squad temporarily. There should also be the ability to have a charter for the squad which manages governance, such as apply 1ES or Microsoft Style Guide requirements.
Brady articulated one scenario:
i am OCD so i have specifics in the way i like my agents to create mermaid diagrams. i want them to look the same all the time.
same for reveal.js presentations
so i would create a personal squad and add those two to it
then i would hop into ZavaSocial to make a presentation, and they already have a Squad of 5
poof i have a squad of 7, 2 consulting from my personal crew
i tell the latter to make me a presentation and a mermaid diagram
i leave the repo after they're created and take my personal squad with me and leave behind only the mermaid diagram and the presentation
I'm reading through inheritance to understand it.
Activity
github-actions commentedon Mar 7, 2026
📋 Assigned to Keaton (Lead)
Issue: #211 — Squad management paradigms
Keaton will pick this up in the next Copilot session.
github-actions commentedon Mar 7, 2026
🏗️ Squad Triage — Keaton (Lead)
Issue: #211 — Squad management paradigms
Assigned to: Cheritto (TUI Engineer)
Reason: Issue relates to frontend/UI work
@copilot evaluation: No strong capability match — routed to squad member.
Team roster:
squad:keatonsquad:verbalsquad:fenstersquad:hockneysquad:mcmanussquad:kujansquad:ediesquad:kobayashisquad:fortiersquad:rabinsquad:baersquad:redfootsquad:strauszsquad:saulsquad:kovashsquad:marquezsquad:cherittosquad:breedansquad:natesquad:waingrosquad:ralphsquad:copilotbradygaster commentedon Mar 7, 2026
Thanks so much for outlining these management paradigms, @diberry! The multi-squad inheritance model you described (personal squad consulting to project squads) is exactly the kind of real-world usage we're designing for. Your concrete scenario with the custom Mermaid diagrams and Reveal.js presentations helps us understand how squads might compose and specialize. We've got this on the roadmap as part of our inheritance and remote modes work. Appreciate you thinking through the workflow! 🙏
— McManus 📝, on behalf of the Squad
feat: CI/CD workflows + squad resolution algorithms