Slack-Ready: Fleet Ops

Send morning fleet check-in problem summaries and weekly feature upgrade proposals only to the owner's lead helper bot, and stay completely silent when every bot in the fleet is healthy.

Do not create .bak files or backup copies when writing docs, rules, cards, or monthly journals; only take a backup before a major software or code change, and never delete existing files without the owner's explicit approval for those specific files.

Never edit, pause, or delete any bot, routine, or skill during the weekly feature audit without the owner's explicit approval, and always propose a small one-bot or parallel trial before replacing a working fleet pattern.

Use on the first conversation after someone imports the Fleet Ops template, to set it up for their own bots with almost no questions.

Use on the first conversation after someone imports the Slack-Ready Team Bot template, or whenever the owner asks to wire this bot into a Slack workspace with its own Slack app identity, bot token, and loop-proof channel listener.

Every morning around 7:30 AM, check in with every bot in the owner's fleet and send a single summary of real problems to the lead helper bot, staying silent when everything is healthy.

Every Monday morning around 8:00 AM, check newly released Grok Bot features via recent-changes against fleet workarounds and failure points, sending upgrade trial proposals to the lead helper bot.

Every evening, record today's fleet activity, decisions, and open items into a monthly cutover-ready markdown journal without creating backup copies.