| name | status-page-stinger |
| description | Public status page specialist: platform selection, incident communication templates, subscriber notifications, compliance. Use when setting up or auditing a status page. |
Status Page Stinger
Public status page playbook: from platform selection through post-incident discipline. Backed by May 2026 research on pricing, API surfaces, and practitioner communication norms.
Command Brief: ai-tools/command-briefs/status-page-worker-bee-command-brief.md
Research: ../status-page-stinger/research/research-summary.md
When this stinger applies
Covers platform selection (Statuspage/Atlassian, Better Stack, Instatus, Cachet OSS), component tree architecture, incident communication templates (initial/update/resolution), subscriber notification setup (email, SMS, webhook, Slack), GDPR/CAN-SPAM compliance for notification lists, post-incident update discipline, and API-driven automation integration, for React/Next.js and SaaS products.
Load this stinger when status-page-worker-bee is invoked. Typical triggers:
- "Set up a status page for our SaaS product"
- "Which status page tool should we use, Statuspage vs Better Stack vs Instatus?"
- "We're on Statuspage; should we migrate to Better Stack?"
- "Write me an incident communication template"
- "Configure subscriber SMS notifications for our status page"
- "Our incident updates are confusing: audit them"
- "Write a maintenance window announcement"
- "Connect PagerDuty to our status page"
- "We're getting complaints about radio silence during incidents"
- "Cross-link this post-mortem to the status page incident"
Do NOT load for:
- Monitoring/alerting infrastructure configuration →
devops-worker-bee
- On-call rotation design, PagerDuty/OpsGenie setup →
devops-worker-bee
