Player profile
Squad
An open-source GitHub Copilot-based agent team system where specialists live in the repo, keep memory, route work, and run in parallel.
Profile
Where it fits
Squad gives GitHub Copilot a repo-native AI development team: specialist agents live in `.squad/`, keep their own history, share decisions, and work from project context that can be committed with the codebase.
It belongs in Open Orchestrators because the central object is the team layer itself: coordinator routing, specialist roles, persistent memory, parallel execution, issue triage, and recovery breadcrumbs rather than one-off chat sessions.
The public docs mark Squad as alpha, so it should be treated as an early but high-signal open-source project.
Builder web analytics
Measure projects built with Squad
Squad teams can ship changes through persistent repo-native agents. Agent Analytics gives the follow-up Squad session user-event data so the team can learn whether the shipped work moved real customers.
Squad runs through GitHub Copilot and repo-local team files. If the coding-agent environment already has the Agent Analytics skill from skills.sh, let the Squad-guided agent use that workflow; otherwise add event reporting through the Agent Analytics CLI/API, verify events, and fetch results in the next Squad session.
First loop to measure
- a Squad team routes work to specialist agents for a page, docs path, onboarding flow, app surface, or growth experiment
- the shipped surface reports visits, sources, CTA clicks, signup, activation, retention, and conversion events to Agent Analytics
- a lead or analyst-style Squad agent fetches Agent Analytics data and compares the changed path with the prior period
- the finding is recorded back into Squad decisions or history and becomes the next routed improvement
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including Squad-built page, traffic source, CTA click, signup, activation event, funnel step, or shipped change. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which Squad-built page, traffic source, CTA click, signup, activation event, funnel step, or shipped change moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.Related