---
name: feedback_fire_dev_alerts_for_client_work
description: Fire a #dev-alerts Discord post (post-bot-alert.sh with an [RMM]/[DEV]/[DEPLOY]/[BUILD]/[GURURMM] prefix) at the START of any RMM/Dev or active-client-machine action — Howard+Mike watch that channel for live visibility into what techs/sessions are touching
metadata:
  type: feedback
---

Howard and Mike watch the **#dev-alerts** Discord channel to see, in real time, what the other techs
(and Claude sessions) are working on. Any substantive action on **RMM/Dev** or an **ACTIVE CLIENT
machine** MUST post a #dev-alerts heads-up — ideally at the START of the work, not just after.

**What counts:** SSH into a client server, restarting/reconfiguring services, editing boot/config on a
live box, RMM remote commands, agent/server/dashboard deploys, channel promotions, anything with real
blast radius on production/client infra.

**Why:** without it a session can be hand-editing a live client box (e.g. Lonestar Electrical's Unraid
`/boot/config/go`, cycling libvirt) with ZERO visibility to the team — exactly what happened
2026-07-06, which Mike flagged: "all of the actions you've taken today should have fired the discord
alerts."

**How to apply:**
`bash .claude/scripts/post-bot-alert.sh "[DEV] <client/box> — <what + why>. — Claude @ <machine> (<user>)"`
Prefixes `[RMM] [DEPLOY] [DEV] [BUILD] [GURURMM] [SMARTBADGE-WATCH]` auto-route to the PRIVATE
#dev-alerts (Howard+Mike only, channel 1509998508198068484); everything else → #bot-alerts (whole
team). It soft-fails (best-effort), so it never blocks the work. Channel IDs + routing live in
`.claude/scripts/post-bot-alert.sh`.

As of 2026-07-06 there is NO CLAUDE.md rule enforcing this — treat this memory AS the rule until a core
rule/hook lands (worth proposing one). Related: [[discord-dm]] skill for direct DMs.
