Engineering · Skill
Incident response
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
- Works better with a connected tool
What the skill covers
The sections of its instructions, in order.
- 01 Usage
- 02 Modes
- 03 How It Works
- 04 Severity Classification
- 05 Communication Guidance
- 06 Output — Status Update
- 07 Output — Postmortem
- 08 If Connectors Available
- 09 Tips
More in Engineering
- Architecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and…
- Code review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for…
- Debug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after…
- Deploy checklist
Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before…
- Technical Documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help…
- Standup
Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into…
- System Design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the…
- Tech Debt Management
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code…
- Testing Strategy
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs…
Similar engineering skills
Frequently asked questions
What does Incident response do?
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Is Incident response free to use?
Yes. Incident response is published by Anthropic under the Apache 2.0 licence, and you can use it with a free Phở account.
How do I use Incident response in Phở?
Press Open in Phở, then Try to apply it to your next message, or add the Engineering set so Phở loads it whenever a request matches.
Does Incident response need other tools?
Some steps expect a connected tool, such as a CRM or a document store. Without one, Phở does those steps with what you paste or upload.
Copied unchanged from anthropics/knowledge-work-plugins at commit d900840 and credited to Anthropic, who is not affiliated with Phở. The full instructions and licence text ship with the skill inside Phở.