Repository navigation
SDK init: @copilot routing configured without team.md roster entry #339
Description
Summary
During SDK-first squad setup, @copilot routing rules are added to routing.md but @copilot is NOT added to the team.md roster or squad.config.ts. This creates an inconsistency: the routing table references an agent that doesn't exist in the team definition.
Evidence
routing.mdline 14:Async issue work (bugs, tests, small features) | @copilot 🤖routing.mdIssue Routing table:squad:copilotlabel → assign to @copilotteam.mdMembers section: No @copilot entrysquad.config.ts: No @copilot defineAgent
Expected Behavior
Per squad.agent.md coordinator instructions:
Badge: 🤖 Coding Agent. Always "@copilot" (no casting). No charter — uses copilot-instructions.md.
If the user says "yes" to "Want to include @copilot?", then:
- @copilot should be added to
team.mdroster with 🤖 badge - Routing rules should reference it (✅ already done)
- Capability profile (🟢/🟡/🔴) should be added to team.md
copilot-auto-assignflag should be configured
Currently, routing was pre-configured for @copilot without the user being asked, and the roster entry was never created.
Steps to Reproduce
- Run
squad init --sdk - Complete team setup
- Check
routing.mdfor @copilot references (present) - Check
team.mdfor @copilot in Members table (missing)
Impact
- Issue triage routing to @copilot will fail (no team member to dispatch to)
- Auto-assign behavior cannot work without
copilot-auto-assignflag - Features Context window optimization: decisions.md pruning, spawn template dedup, Init Mode compression #37–docs: MCP, notifications, and plugin marketplace guides #38 (Copilot member, auto-assign) blocked
- Features Self-testing framework: observe UX patterns and identify self-improvement opportunities #23–Research: Run Squad from the Copilot Coding Agent (CCA) #25 partially affected (issue triage can't route to @copilot)
Suggested Fix
Two options:
- Don't pre-configure @copilot routing — only add routing when user opts in during init Phase 2 step 8
- Add @copilot to roster when routing is configured — keep routing, but also add team.md entry with capability profile
Option 1 is cleaner — routing should match roster.
Related
- PRD feature matrix: Features Self-testing framework: observe UX patterns and identify self-improvement opportunities #23–Research: Run Squad from the Copilot Coding Agent (CCA) #25 (issue lifecycle), Context window optimization: decisions.md pruning, spawn template dedup, Init Mode compression #37–docs: MCP, notifications, and plugin marketplace guides #38 (Copilot member)
- Filed from SdkSquad test bed during SDK/markdown parity testing
Activity
github-actions commentedon Mar 10, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #339 — SDK init: @copilot routing configured without team.md roster entry
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:copilotbradygaster commentedon Mar 10, 2026
Update from SDK-First Parity Testing (2026-03-10)
Finding: The @copilot routing was pre-configured during init without the user being asked the opt-in question from Phase 2 step 8 ("Want to include @copilot?"). This creates a state where:
routing.mdline 14:Async issue work | @copilot 🤖— presentrouting.mdIssue Routing table:squad:copilotlabel routing — presentteam.mdMembers roster: @copilot — missingsquad.config.ts: @copilot — missingTwo options for fix:
Recommendation: Option 1. The coordinator instructions say @copilot is opt-in (Phase 2 step 8). Pre-configuring routing without opt-in violates that contract.
Issue triage tested successfully despite this gap: Dozer analyzed issues and correctly identified which squad:{member} labels to apply using the bradygaster/squad team structure (Apollo mission control cast). The triage mechanism works — it's just the @copilot roster entry that's missing.
Full test results: #341
feat: rich progress indicators for agent work (github#357)
feat: accessibility hardening and guidelines (github#359)
github-actions commentedon Mar 13, 2026
squad:hockney. Check.squad/team.md(or.ai-team/team.md) for valid member names.github-actions commentedon Mar 13, 2026
📋 Assigned to FIDO (Quality Owner)
Issue: #339 — SDK init: @copilot routing configured without team.md roster entry
FIDO will pick this up in the next Copilot session.
fix: SDK init trio - Ralph, @copilot routing, config sync (#337, #338, …
fix: SDK init trio — #337 config sync, #338 Ralph in init, #339 remov…
fix: SDK init trio — #337 config sync, #338 Ralph in init, #339 remov…
fix: SDK init trio - routing, Ralph, and config wiring (#337, #338, #339
bradygaster commentedon Mar 15, 2026
Fixed and merged to dev in the irritating bugs sprint.