unified-notifications-ops

Use this skill when the real problem is not a missing ping. The real problem is a fragmented notification system. The job is to turn scattered events into one operator surface with: Start from what already exists: Prefer ECC-native orchestration over telling the user to adopt a separate notification product. Treat the lane as: The goal is fewer, better notifications. If the workspace has no severity model, build one before proposing automation. List: Call out what ECC already owns. For each event family, answer: Use these defaults: Look for: Prefer: For each real notification need, define: If ECC already has the primitive, prefer: End with: - clear severity - clear ownership - clear routing - clear follow-up action - the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email - CI failures, review requests, issue updates, and operator events are arriving in disconnected places - the current setup creates noise instead of action - the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane - the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy - GitHub issues, PRs, reviews, comments, and CI - Linear issue/project movement - local hook events and session lifecycle signals - desktop notification primitives - connected email/chat surfaces...