Works with the AI Agents you already use
major incident coordination playbook builder
- **Event Timeline** produces a time-stamped task list starting from the initial declaration time through the review horizon.
$1.99
major incident coordination playbook builder
Example session with this skill installed
Draft a playbook for incident INC-882 declared at 2024-10-12T14:00Z. Sev1 on 'payment-gateway'. I have the roster and policy files ready. Access is restricted to 'payment' services.
- Read your context and instructions
- Compiled the major incident coordination
The incident coordination plan for INC-882 has been drafted using the provided severity profiles and roster data. All timings are calculated from the declaration time of 14:00 UTC.
Major Incident Coordination Playbook (draft) — INC-882, 2024-10-12
1. Incident, scope and assumptions
- Incident ID: INC-882 (Sev1)
- Declared: 2024-10-12 14:00 UTC
- Horizon End: 2024-10-12 18:00 UTC
- Scope: 1 service (payment-gateway). 2 services excluded by access scope.
- Assumptions: Internal update interval set to 30m. Analytical estimate — validation required.
2. Command roles (proposed)
| Role | Proposed holder | Status | Candidates |
|---|---|---|---|
| Incident Commander | user_99 | Assigned | 2 |
| Comm Lead | user_42 | Assigned | 1 |
| Scribe | UNFILLED | Information gap | 0 |
3. Communications plan
| Group | Audience | Channel | Interval (min) | Approver | Notices | First | Last |
|---|---|---|---|---|---|---|---|
| Exec | Internal | 60 | mgmt_01 | 4 | 14:15 | 17:15 | |
| Customers | External | StatusPage | 30 | Management decision required | 8 | 14:30 | 18:00 |
4. Escalation plan
| Service | Team | Level | Person | Page at |
|---|---|---|---|---|
| payment-gateway | payments_eng | L2 | dev_21 | 14:15 |
| payment-gateway | payments_eng | L3 | lead_05 | 14:45 |
5. Coordination timeline
| Task | Due (UTC) | Kind | Target | Owner role | Assignee | Needs approval |
|---|---|---|---|---|---|---|
| Initial Comms | 14:15 | Update | Internal | Comm Lead | user_42 | true |
| L2 Escalation | 14:15 | Alert | Team | Commander | user_99 | true |
6. Gaps, warnings and items for human review
- W04: Scribe role remains unfilled; no qualified personnel available in provided roster.
- Review: Validate stakeholder contact list for 'External' audience before 14:30 UTC.
7. Approval status
- State: PENDING
- Approved by: None
Nothing has been executed. This draft supports, and does not replace, the incident manager's judgment and management's decision.
Next steps
- Review the proposed Incident Commander and Comm Lead assignments.
- Confirm the 30-minute update interval for the customer StatusPage.
- Manually assign a Scribe from the backup roster.
Connects securely to your tools. The creator never sees your data.
About this skill
Major incidents stall when roles are unclear, stakeholder updates lag, and escalation paths aren't predefined. This skill builds a technical coordination playbook from your incident data and rosters.
What it does
- Role Assignment proposes candidates for command roles based on qualifications, availability, and recorded consent.
- Communication Cadence generates a schedule for updates across internal, executive, customer, and regulatory stakeholder groups.
- Escalation Ladders maps functional and hierarchical checkpoints for each service owning team on a fixed clock.
- Event Timeline produces a time-stamped task list starting from the initial declaration time through the review horizon.
- Access Control Enforcement automatically excludes and counts services or personnel outside the provided access scope or consent records.
How it works
- Supply the incident details, service records, team rosters, and your organization's timing policies.
- The skill validates the input against a strict schema to ensure all required identifiers and timestamps are present.
- A deterministic script processes the data to calculate role assignments and timing intervals without manual estimation.
- The skill generates a draft playbook structured for immediate human review and approval.
Frameworks & tools
This skill uses a Python-based logic engine to process JSON inputs and generate Markdown reports. It integrates with ITSM data structures and follows standard coordination patterns for IT service incidents.
Why this beats prompting it yourself
Generic prompts often hallucinate person names or ignore complex access constraints. This tool uses a deterministic script to ensure every timestamp and role assignment is calculated based on your specific policy and roster data, never fabricating details.
Use cases
- Draft an incident coordination plan immediately after declaring a Sev1 or Sev2.
- Verify if current on-call rosters can fill all required incident command roles.
- Standardize the communication frequency for executive and external stakeholders.
- Establish clear functional escalation triggers for technical owning teams.
Known limitations
Does not support cybersecurity incident response tasks like forensics or containment. It is a drafting tool only and cannot page people or send notifications directly.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
No support for security forensics or containment. Cannot execute pages or notices. Requires specific JSON input schema for deterministic results.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 days ago