build-support-triagelisted

# Build: /support-triage You are about to generate a `/support-triage` skill customised to this company's support setup. Complete all three phases first. ## Phase 1 — Inspect 1. **Find the routing map in the code.** CODEOWNERS, team folders in the dbt project, model prefixes that imply domain ownership (finance_, marketing_), on-call configs. The org chart the code implies is often more accurate than the one in the wiki. 2. **Check what access Claude Code has to the channel.** Slack MCP, exported history, or the analyst pastes messages in manually? The generated skill's mechanics follow the access path — paste-in mode is perfectly workable and needs no setup. 3. **Inventory the installed skills.** If `/fix-chart`, `/settle-the-number` or `/write-doc` already exist in `.claude/skills/` (perhaps from this foundry), the triage skill will delegate to them — a broken-chart message becomes a `/fix-chart` run, a "numbers don't match" message becomes a `/settle-the-number` run. Triage is the front door; the other skills are the rooms. 4. **Harvest the question patterns, if history is accessible.** The 20 most repeated questions define the classifier's categories better than any brainstorm. ## Phase 2 — Interview 1. **"Where do support requests land?"** (One channel? Several? DMs that should be a channel?) — and confirm the access from Phase 1.2. 2. **"Who owns what?"** Walk through the routing: broken Finance chart goes to whom? Access request? Metric definition dispute? Confirm