| 1 | # Work Routing |
| 2 | |
| 3 | How to decide who handles what. |
| 4 | |
| 5 | ## Routing Table |
| 6 | |
| 7 | | Work Type | Route To | Examples | |
| 8 | |-----------|----------|----------| |
| 9 | | Data crawling, GitHub API, Actions workflows | Bender | Build crawler, fix API pagination, add rate limiting | |
| 10 | | Trend analysis, content curation, critical thinking | Farnsworth | Analyze weekly data, identify trends, write summaries | |
| 11 | | Frontend, site design, GitHub Pages, templates | Amy | Build site layout, create report templates, fix styling | |
| 12 | | Visual design, brand assets, icons, design system | Calculon | Design tokens, icon, OG image, layout mockups, design review | |
| 13 | | Architecture, scope, priorities, editorial direction | Leela | Decide tech stack, review architecture, set priorities | |
| 14 | | Code review | Leela | Review PRs, check quality, approve/reject | |
| 15 | | Security review, threat analysis, vulnerability triage | Hermes | Review PRs for security, triage Dependabot/CodeQL alerts, threat modeling | |
| 16 | | DevSecOps pipeline, guardrail tooling, hooks, dependency/secret scanning | URL | Set up ruff/checkov/zizmor CI gates, install git hooks, wire SARIF, pin actions, phased rollout | |
| 17 | | Prompt injection, AI safety, harmful content, dark-pattern review | Nibbler | Prompt/input-output guardrails, untrusted-content fencing, canary checks, RAI review, accessibility/dark-pattern sweeps | |
| 18 | | SEO, titles, meta tags, structured data, search optimization | Zapp | Page title quality, meta descriptions, OpenGraph/JSON-LD, heading hierarchy, content discoverability | |
| 19 | | Testing, QA, validation | Fry | Write tests, validate pipeline, find edge cases | |
| 20 | | Scope & priorities | Leela | What to build next, trade-offs, decisions | |
| 21 | | Session logging | Scribe | Automatic — never needs routing | |
| 22 | |
| 23 | ## Issue Routing |
| 24 | |
| 25 | | Label | Action | Who | |
| 26 | |-------|--------|-----| |
| 27 | | `squad` | Triage: analyze issue, assign `squad:{member}` label | Lead | |
| 28 | | `squad:{name}` | Pick up issue and complete the work | Named member | |
| 29 | |
| 30 | ### How Issue Assignment Works |
| 31 | |
| 32 | 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. |
| 33 | 2. When a `squad:{member}` label is applied, that member picks up the issue in their next session. |
| 34 | 3. Members can reassign by removing their label and adding another member's label. |
| 35 | 4. The `squad` label is the "inbox" — untriaged issues waiting for Lead review. |
| 36 | |
| 37 | ## Trigger Phrases |
| 38 | |
| 39 | | Phrase | Action | |
| 40 | |--------|--------| |
| 41 | | "take a nap and reskill" | Team-wide reskill cycle — follow `.squad/templates/skills/reskill/SKILL.md` | |
| 42 | |
| 43 | ## Rules |
| 44 | |
| 45 | 1. **Eager by default** — spawn all agents who could usefully start work, including anticipatory downstream work. |
| 46 | 2. **Scribe always runs** after substantial work, always as `mode: "background"`. Never blocks. |
| 47 | 3. **Quick facts → coordinator answers directly.** Don't spawn an agent for "what port does the server run on?" |
| 48 | 4. **When two agents could handle it**, pick the one whose domain is the primary concern. |
| 49 | 5. **"Team, ..." → fan-out.** Spawn all relevant agents in parallel as `mode: "background"`. |
| 50 | 6. **Anticipate downstream work.** If a feature is being built, spawn the tester to write test cases from requirements simultaneously. |
| 51 | 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. |
| 52 | 8. **AI-safety review** — work that changes prompts, imported external text, generated content, or user-facing AI output routes through Nibbler before merge. |
| 53 | 9. **DevSecOps pipeline & guardrails** — changes to CI security/lint tooling (ruff, checkov, zizmor, Bandit, pip-audit), git hooks, or dependency/secret scanning route to URL. Infra, `Dockerfile`/`Containerfile`, and `.github/workflows/` changes get a URL (pipeline) review alongside Hermes (security). |