status-page-wasp-drone — Claude Code subagent
status-page-wasp-drone is a Claude Code subagent for choosing a status platform, designing components, writing incident messages, and configuring subscriber notifications.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat status-page-wasp-drone does
status-page-wasp-drone builds a status page from platform choice through first subscriber notification. It guides you through Statuspage, Better Stack, Instatus, and Cachet (open source); maps your service inventory to components; drafts incident messages with mandatory next-update time; sets up email, SMS, webhook, and Slack; and connects monitoring to automated page updates.
The subagent watches for two critical gaps: manually updating the page during an outage (the on-call engineer is the worst person for this task), and incomplete notifications (a message without a next-update time leaves readers in the dark). It also enforces GDPR and CAN-SPAM: double opt-in and an unsubscribe link are not optional.
Out of scope: monitoring and alerting setup (devops-wasp-drone), on-call rotations and incident process design (devops-wasp-drone), or runbook authorship for incident response (runbook-writing-wasp-drone).
What it helps with
- choose a status platform that fits your budget and toolchain
- map services to customer-facing components
- draft incident messages with locked next-update time
- route notifications to email, SMS, and Slack with compliance
- automate page updates via monitoring and PagerDuty
Example prompts for the agent
- Compare Statuspage versus Better Stack for a SaaS with 50k users—which wins on cost and features?
- Write an initial incident message template with a mandatory next-update time slot
- Set up subscriber notifications over email and Slack while enforcing GDPR and unsubscribe requirements
How to install status-page-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/status-page-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/status-page-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/status-page-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about status-page-wasp-drone
How do I install status-page-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest. The subagent loads in .claude/agents/status-page-wasp-drone.md.
What does status-page-wasp-drone do?
It helps you pick a status platform, design component trees and notifications, write incident message templates, and wire monitoring to automated page updates. The goal is silence-free outages and reliable subscriber alert delivery.
How is status-page-wasp-drone different from devops-wasp-drone?
status-page-wasp-drone owns the public status page, customer-facing messages, and subscriber notifications. devops-wasp-drone owns monitoring, alerting rules, and on-call setup. Do not mix them: one speaks to customers; the other listens to infrastructure.