Repository navigation
Closed
Labels
go:needs-researchNeeds investigationNeeds investigationnext-upPriority queue — next issues to workPriority queue — next issues to workpriority:p1This sprintThis sprintsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membertype:featureNew capabilityNew capability
Description
Summary
Implementation plan for the Ambient Personal Squad feature, based on Flight's architecture review and 19-task breakdown.
Background
Flight validated the 20KB design doc and identified 5 gaps (all resolved):
- No
resolvePersonalAgents()function signature — added to plan - Scenario 9 contradiction: personal agents writing to project orchestration log (violates ghost protocol) — coordinator writes audit trail instead
--team-rootscope undefined — additive CLI flag onsquad init, backward compatsquad personal initmissing — bootstrapping path for first-time users- No
SQUAD_NO_PERSONALkill switch — env var gates ambient discovery at earliest point
Implementation Plan — 4 PRs
PR #1 — SDK Foundation (EECOM)
ResolvedSquadPaths.personalDir— add personal dir to resolved pathsresolvePersonalSquadDir()— platform-aware personal squad directory resolutionPersonalAgentMetatype — metadata for personal agents (origin: 'personal')resolvePersonalAgents()— discover and load personal agentsmergeSessionCast()— merge personal agents into session castensureSquadPathTriple()— extend dual-root path guard to triple-root for personal dirsSQUAD_NO_PERSONALenv var — kill switch for ambient discovery
PR #2 — CLI Surface (EECOM, depends on PR #1)
squad personal init— bootstrap a personal squadsquad personal list— list personal agentssquad personal add— add a personal agentsquad personal remove— remove a personal agentsquad cast— show current session cast (project + personal)--team-rootflag — explicit team root override- Wiring + package exports
PR #3 — Governance (Procedures, concurrent with PR #1)
squad.agent.mdupdates for personal squad awareness- Ghost Protocol template — rules for personal agent behavior in project context
personal-charter.mdtemplate — charter template for personal agents- Consult mode detection and routing rules
PR #4 — Tests (Sims, after PR #1 + #2)
- E2E ambient discovery tests
- Ghost Protocol enforcement tests
- Routing scenario tests (personal vs project agents)
- Unit tests for all SDK functions
MVP
PR #1 + PR #3 — users see ambient cast immediately. squad personal commands (PR #2) are quality-of-life on top.
Key Decisions
- Personal agents tagged with
origin: 'personal'and Ghost Protocol applied - Audit trail is coordinator-written in project orchestration log (personal agents don't write to project state)
SQUAD_NO_PERSONALenv var gates ambient discovery at the earliest point- Dual-root path guard extended to triple-root (
ensureSquadPathTriple) for personal dirs - Personal squad paths resolved via platform detection (never hard-coded)
- Resolution priority: explicit (CLI flag) > project config > env var > git remote mapping > path mapping > default
Status
Design validated. Ready for EECOM to start PR #1.
Metadata
Metadata
Assignees
Labels
go:needs-researchNeeds investigationNeeds investigationnext-upPriority queue — next issues to workPriority queue — next issues to workpriority:p1This sprintThis sprintsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membertype:featureNew capabilityNew capability
Activity
github-actions commentedon Mar 22, 2026
📋 Assigned to Sims (E2E Test Engineer)
Issue: #508 — Implementation: Ambient Personal Squad (#329 + #344)
Sims will pick this up in the next Copilot session.
github-actions commentedon Mar 22, 2026
📋 Assigned to EECOM (Core Dev)
Issue: #508 — Implementation: Ambient Personal Squad (#329 + #344)
EECOM will pick this up in the next Copilot session.
github-actions commentedon Mar 22, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #508 — Implementation: Ambient Personal Squad (#329 + #344)
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work
@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotgithub-actions commentedon Mar 22, 2026
📋 Assigned to Procedures (Prompt Engineer)
Issue: #508 — Implementation: Ambient Personal Squad (#329 + #344)
Procedures will pick this up in the next Copilot session.
bradygaster commentedon Mar 22, 2026
@jsturtevant - thoughts?
feat(sdk): add personal squad resolution and ambient discovery (#508)
9 remaining items
docs(.squad): log mega-session — #508 complete, #525 complete, #498 a…
feat(sdk): add personal squad resolution and ambient discovery (#508) (…
feat(cli): personal squad CLI commands (#508) (#538)
feat(governance): add personal squad governance layer (#508) (#539)
test: add personal squad unit and integration tests (#508)
test: add personal squad unit and integration tests (#508) (#541)
bradygaster commentedon Mar 23, 2026
All 4 PRs merged: #536 (SDK foundation), #538 (CLI commands), #539 (governance), #541 (tests). Ambient Personal Squad is shipped.
dat-intellis commentedon Mar 24, 2026
This sounds like a great addition, but I must admit I'm confused as to how Im supposed to use this based on the currently available documentation on personal squads: https://bradygaster.github.io/squad/docs/guide/personal-squad/#4-use-case-your-side-projects-get-a-team
Any pointers?
feat(observability): add OTel shell metrics — session, latency, errors (
[dgrep-cli] Phase 1.2: Config file management (github#102) (github#124)