What problem does it solve? Engineering teams receive CI failures, review requests, issue updates, and operator events across disconnected channels like GitHub, Linear, desktop alerts, and chat, creating noise instead of action. This Skill turns fragmented notification streams into a single operator surface with clear severity, ownership, routing, and follow-up actions. ## Core Features & Use Cases - Surface Inventory: Audits existing event sources, channels, hooks, duplicate paths, and silent failure gaps before proposing changes. - Severity-Based Routing: Classifies events into critical, high, medium, and low tiers, then maps each to interrupt, digest, queue, or log-only handling. - Duplicate Collapse: Merges the same event appearing across GitHub, Linear, and local logs into one canonical summary with one owner and one primary channel. - Use Case: A team drowning in noisy CI failure pings across three tools uses this Skill to decide what should interrupt immediately versus land in a daily digest, then designs one ECC-native notification lane. ## Quick Start Audit my current GitHub, Linear, and local hook notifications and design a unified routing plan that separates what should interrupt me from what belongs in a digest.
