task-routing

# Task Routing Route issues to the correct repo using the routing config from CLAUDE.md. Part of the Personal Corp framework: `project-init` → **`task-routing`** → `weekly-planning` / `weekly-retro`. ## How It Works ```dot digraph routing { "New task" -> "Read routing config from CLAUDE.md"; "Read routing config from CLAUDE.md" -> "Match keywords → target repo"; "Match keywords → target repo" -> "Check duplicates in target repo"; "Check duplicates in target repo" -> "Duplicate found?" [shape=diamond]; "Duplicate found?" -> "Update existing issue" [label="yes"]; "Duplicate found?" -> "Check W-label exists in target repo" [label="no"]; "Check W-label exists in target repo" -> "Create issue in target repo"; } ``` ## Step 1: Read Routing Config Find the `### Task Routing` section in CLAUDE.md of the **current project** (or the HQ repo if running from there): ```yaml ### Task Routing (which issues go where) routing: - pattern: "bot, broadcast, onboarding" repo: owner/bot-repo - pattern: "content, lessons" repo: owner/content-repo - pattern: "strategy, cross-cutting" repo: owner/main-repo ``` This config is created by `project-init`. If it doesn't exist — STOP and tell the user to run `project-init` first. ## Step 2: Match Pattern Match the task description against routing patterns. Rules: - Match by **keywords in the task**, not by where you happen to be running - If multiple patterns match, pick the most specific - If no pat...