Setting the file. One moment.
Subchapter 11.17
routing.mdMarkdown3 KBView on GitHub
| Work Type | Route To | Examples |
|---|---|---|
| {domain 1} | {Name} | {example tasks} |
| {domain 2} | {Name} | {example tasks} |
| {domain 3} | {Name} | {example tasks} |
| Code review | {Name} | Review PRs, check quality, suggest improvements |
| Testing | {Name} | Write tests, find edge cases, verify fixes |
| Scope & priorities | {Name} | What to build next, trade-offs, decisions |
| Async issue work (bugs, tests, small features) | @copilot 🤖 | Well-defined tasks matching capability profile |
| Session logging | Scribe | Automatic — never needs routing |
| Label | Action | Who |
|---|---|---|
squad | Triage: analyze issue, evaluate @copilot fit, assign squad:{member} label | Lead |
squad:{name} | Pick up issue and complete the work | Named member |
squad:copilot | Assign to @copilot for autonomous work (if enabled) | @copilot 🤖 |
squad label, the Lead triages it — analyzing content, evaluating @copilot’s capability profile, assigning the right squad:{member} label, and commenting with triage notes.squad:copilot instead of a squad member.squad:{member} label is applied, that member picks up the issue in their next session.squad:copilot is applied and auto-assign is enabled, @copilot is assigned on the issue and picks it up autonomously.squad label is the “inbox” — untriaged issues waiting for Lead review.When triaging, the Lead should ask:
mode: "background". Never blocks.mode: "background".squad:{member} label is applied to an issue, route to that member. The Lead handles all squad (base label) triage.team.md. Route 🟢 good-fit tasks to squad:copilot. Flag 🟡 needs-review tasks for PR review. Keep 🔴 not-suitable tasks with squad members.