Incident Status Page Ops Review

Use this skill to convert incident status page, public communication, subscriber notification, maintenance, component, and post-incident questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

1. Identify product components, customer segments, incident severity, detection sources, SLO/customer impact, communication owners, support load, legal/security constraints, and current status page gaps.
2. Read references/incident-status-page-ops-patterns.md.
3. Classify communication as investigating, identified, monitoring, resolved, scheduled maintenance, degraded performance, partial outage, security-sensitive, or post-incident follow-up.
4. Define component taxonomy, declaration threshold, update cadence, template, approval path, subscriber channels, support coordination, and history/postmortem linkage.
5. Produce status-page ops plan, state machine, decision table, event schema, communication checklist, and incident drill plan.

When not to use

• Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails