incident-communication

Draft incident notifications, progress updates, and resolution announcements with blameless language templates.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill incident-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-communication
Source: https://github.com/baphled/dotopencode/tree/main/skills/incident-communication
Command: npx skills add https://github.com/baphled/dotopencode --skill incident-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and professional approach to communicating about security and operational incidents, ensuring stakeholders are informed and trust is maintained.

Core Features & Use Cases

  • Incident Notification: Draft initial alerts when a production issue is detected.
  • Progress Updates: Provide regular, consistent updates during an ongoing incident.
  • Resolution & Post-Mortem: Announce resolutions and draft post-incident summaries.
  • Use Case: A critical service is down. Use this Skill to draft an initial notification to all users and stakeholders, followed by regular updates on the investigation and resolution progress.

Quick Start

Use the incident-communication skill to draft an initial notification for an issue impacting the user authentication service.

Frequently Asked Questions about incident-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an initial incident notification for a security incident?

To write an initial incident notification, use this Skill to draft professional alerts that inform stakeholders about a detected production issue. It provides structured templates ensuring transparency and appropriate tone from the start of the incident response process.

What is the best way to provide consistent progress updates during an ongoing incident?

The best way to provide progress updates is using structured communication templates that maintain a consistent cadence. This Skill facilitates regular updates during ongoing incidents, ensuring stakeholders remain informed through transparent and blameless language.

Can I use this to draft a post-mortem summary after an operational incident is resolved?

Yes, you can use this Skill to draft post-mortem summaries and resolution announcements after an operational incident is resolved. It helps draft communications that adhere to blameless language principles, maintaining stakeholder trust following the event.

Does this approach support stakeholder management for critical service outages?

Yes, this approach specifically supports stakeholder management for critical service outages by providing templates for initial notifications, progress updates, and resolution announcements. It ensures effective communication by adhering to core principles of transparency and consistent cadence.

What tone should I use when communicating about security incidents?

When communicating about security incidents, you should use a professional tone with blameless language. This Skill enforces appropriate tone, transparency, and consistent cadence to ensure effective stakeholder management without assigning individual fault during the response.