feat(skills): add notification-routing skill -- pub-sub channel routing to prevent alert fatigue

[tamirdresher]

Summary

Adds the notification-routing skill — a pub-sub channel routing pattern for agent notifications.

This is an "earned" skill: battle-tested from running 8+ Ralph instances in production where a single notification channel became unusable due to alert fatigue.

Problem

When a Squad grows beyond a few agents, notifications flood a single channel:

• Failure alerts drown in daily briefings
• Tech news buries security findings
• Team members turn off notifications entirely

This is the microservices equivalent of dumping every service's logs into one file.

Solution

Pub-sub topic routing — the same principle as Kafka topics, RabbitMQ routing keys, and AWS SNS topic filtering:

1. .squad/teams-channels.json — config mapping notification types to channel names/IDs
2. CHANNEL: tag convention — agents prefix output with the target channel type
3. Dispatcher pattern — reads the tag, routes to the right channel
4. Provider-agnostic — Teams, Slack, Discord, or any webhook adapter

What's Included

• packages/squad-cli/templates/skills/notification-routing/SKILL.md
• packages/squad-sdk/templates/skills/notification-routing/SKILL.md
• .changeset/notification-routing-skill.md

Design Principles

• ✅ No vendor lock-in — routing config and CHANNEL: tags are provider-agnostic
• ✅ Zero code changes to Squad core — pure skill/config pattern
• ✅ Works with existing .squad/ file architecture
• ✅ Degrades gracefully — falls back to default channel if tag absent

Related

• Closes feat: add PR requirements spec and PR template #672 (tamirdresher/tamresearch1) — Notification routing: multi-channel message delivery
• Part of Phase 1 upstream contributions (fix(sdk): merge skills from both .copilot/skills/ and .squad/skills/ (#77) #669 tamirdresher/tamresearch1)

[bradygaster]

🔍 Squad Team Review

Reviewed by: Procedures (Prompt Architect) — Pass 3 of consensus ceremony
Action: Hold — proposal-first policy applies
Team Consensus: 5/5 AGREE

Review Summary

This PR implements notification-routing improvements, a feature-class change that enables custom routing of system notifications based on skill category and urgency.

Process Note

Per our team's documented proposal-first policy (.squad/decisions.md): "Meaningful changes require a proposal in docs/proposals/ before execution." This is a feature-class change that needs a proposal document before merge.

What's Needed

1. Create a proposal in docs/proposals/ describing the skill's purpose, integration points, and expected behavior
2. Retarget this PR from main to dev (our staging branch)
3. Once proposal is reviewed and approved, this PR can proceed

Thank you for the contribution! The implementation looks solid — we just need the process alignment. 🙏

⏸️ Action: HOLD — awaiting proposal + retarget to dev

[bradygaster]

FIDO Quality Review — PR #625: notification-routing skill

Verdict: ✅ MERGE

Findings

✅ Changeset package names correct: Uses @bradygaster/squad-cli and @bradygaster/squad-sdk — this is the only Tamir PR that gets this right.

✅ File paths correct: Files placed in packages/squad-cli/templates/skills/notification-routing/SKILL.md and packages/squad-sdk/templates/skills/notification-routing/SKILL.md — matches project conventions.

✅ SKILL.md format: Frontmatter has all required fields (name, description, domain, confidence, source). Has Context, Patterns, and Anti-Patterns sections per template.

✅ Additive: No breaking changes, no modifications to existing files beyond the changeset.

✅ Target branch: dev — correct for feature work.

Minor notes (non-blocking):

• Missing trailing newline at end of both SKILL.md files
• No explicit Examples section (template has one), but patterns section includes inline examples

Good contribution. Clean and well-structured.