| 1 | # Work Routing |
| 2 | |
| 3 | How to decide who handles what. |
| 4 | |
| 5 | ## Routing Table |
| 6 | |
| 7 | | Work Type | Route To | Examples | |
| 8 | |-----------|----------|----------| |
| 9 | | {domain 1} | {Name} | {example tasks} | |
| 10 | | {domain 2} | {Name} | {example tasks} | |
| 11 | | {domain 3} | {Name} | {example tasks} | |
| 12 | | Code review | {Name} | Review PRs, check quality, suggest improvements | |
| 13 | | Testing | {Name} | Write tests, find edge cases, verify fixes | |
| 14 | | Scope & priorities | {Name} | What to build next, trade-offs, decisions | |
| 15 | | Session logging | Scribe | Automatic — never needs routing | |
| 16 | | RAI review | Rai | Content safety, bias checks, credential detection, ethical review | |
| 17 | |
| 18 | ## Issue Routing |
| 19 | |
| 20 | | Label | Action | Who | |
| 21 | |-------|--------|-----| |
| 22 | | `squad` | Triage: analyze issue, assign `squad:{member}` label | Lead | |
| 23 | | `squad:{name}` | Pick up issue and complete the work | Named member | |
| 24 | |
| 25 | ### How Issue Assignment Works |
| 26 | |
| 27 | 1. When a GitHub issue gets the `squad` label, the **Lead** triages it — analyzing content, assigning the right `squad:{member}` label, and commenting with triage notes. |
| 28 | 2. When a `squad:{member}` label is applied, that member picks up the issue in their next session. |
| 29 | 3. Members can reassign by removing their label and adding another member's label. |
| 30 | 4. The `squad` label is the "inbox" — untriaged issues waiting for Lead review. |
| 31 | |
| 32 | ## Rules |
| 33 | |
| 34 | 1. **Eager by default** — spawn all agents who could usefully start work, including anticipatory downstream work. |
| 35 | 2. **Scribe always runs** after substantial work, always as `mode: "background"`. Never blocks. |
| 36 | 3. **Quick facts → coordinator answers directly.** Don't spawn an agent for "what port does the server run on?" |
| 37 | 4. **When two agents could handle it**, pick the one whose domain is the primary concern. |
| 38 | 5. **"Team, ..." → fan-out.** Spawn all relevant agents in parallel as `mode: "background"`. |
| 39 | 6. **Anticipate downstream work.** If a feature is being built, spawn the tester to write test cases from requirements simultaneously. |
| 40 | 7. **Issue-labeled work** — when a `squad:{member}` label is applied to an issue, route to that member. The Lead handles all `squad` (base label) triage. |