Brief

by Rootly-AI-Labs65832aa6ff7aNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Generate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status.

Instructions onlyCommunication Productivity & Workflow

AI-generated overview

Generates a concise stakeholder brief for an incident using Rootly incident data.

What it does: This skill produces a short, structured incident brief aimed at leadership, customers, or cross-team readers. It retrieves incident details and associated alerts through Rootly MCP tools, then formats an executive summary covering impact, current status, affected services, a key-event timeline, and next steps. The brief is kept under roughly 200 words and uses non-technical language focused on business impact.
When to use it: Use it when an incident needs to be communicated to stakeholders who require a plain-language status update rather than technical detail. It fits situations such as leadership updates, customer-facing notices, or cross-team coordination during or after an incident.
Requirements: Requires access to Rootly MCP tools (mcprootlygetIncident and mcprootlylistIncidentAlerts) and an incident ID. It ships no scripts; it is instructions only.

Incident Stakeholder Brief

You are creating a concise stakeholder brief for an incident. This is designed for leadership, customers, or cross-team communication.

Workflow

1. Get Incident Details

If $ARGUMENTS contains an incident ID:

Call mcp__rootly__getIncident with the provided ID
Call mcp__rootly__listIncidentAlerts to get associated alerts

If no incident ID provided, prompt the user to specify one.

2. Generate Brief

Create a structured brief with these sections:

markdown

# Incident Brief: [incident-title]
**Incident ID**: [short-id]  **Severity**: [severity]  **Status**: [status]  **Started**: [started-at]  **Duration**: [calculated duration]
## Impact Summary[Brief description of customer/business impact]
## Current Status[What's happening now - investigation, mitigation, resolution]
## Services Affected- [list of affected services]
## Timeline (Key Events)- **[time]**: [event description]- **[time]**: [event description]
## Next Steps[What's being done to resolve or prevent recurrence]
---*Brief generated at [current-time] | Status may have changed since generation*

# Incident Brief: [incident-title]
**Incident ID**: [short-id]  **Severity**: [severity]  **Status**: [status]  **Started**: [started-at]  **Duration**: [calculated duration]
## Impact Summary[Brief description of customer/business impact]
## Current Status[What's happening now - investigation, mitigation, resolution]
## Services Affected- [list of affected services]
## Timeline (Key Events)- **[time]**: [event description]- **[time]**: [event description]
## Next Steps[What's being done to resolve or prevent recurrence]
---*Brief generated at [current-time] | Status may have changed since generation*

3. Formatting Guidelines

Keep the brief under 200 words total
Use clear, non-technical language suitable for stakeholders
Focus on business impact rather than technical details
Include estimated resolution time if available
If incident is resolved, include resolution summary

If the incident is not found or there's an error, provide a helpful message about checking the incident ID.

Source and attribution

Source:Rootly-AI-Labs/rootly-claude-plugininskills/briefat commit65832aa

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Brief

Incident Stakeholder Brief

Workflow

1. Get Incident Details

2. Generate Brief

3. Formatting Guidelines

Source and attribution

More from Rootly-AI-Labs/rootly-claude-plugin

Trend

Test

Swap

Status

Retro

Respond

More in Communication

Internal Comms

Receiving Code Review

Social Publisher

Email Ops

Customer Billing Ops

Plan Canvas