Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
A full pipeline where an agent team collaborates to generate incident postmortem reports.
Install Incident Postmortem
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 incident-postmortem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .claude/skills/incident-postmortem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .claude/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 incident-postmortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .agents/skills/incident-postmortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .agents/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 incident-postmortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .cursor/skills/incident-postmortem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .cursor/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/revfactory/harness-100.git --path en/25-incident-postmortem/.claude/skills/incident-postmortem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 incident-postmortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .gemini/skills/incident-postmortem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .gemini/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install revfactory/harness-100 incident-postmortemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .github/skills/incident-postmortem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .github/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill incident-postmortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 incident-postmortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/25-incident-postmortem/.claude/skills/incident-postmortem .opencode/skills/incident-postmortem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "incident-postmortem" agent skill from https://github.com/revfactory/harness-100/tree/main/en/25-incident-postmortem/.claude/skills/incident-postmortem into .opencode/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-postmortem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
incident-postmortem- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 689 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A full pipeline where an agent team collaborates to generate incident postmortem reports.
- Works in 3 steps: Preparation (Performed directly by… → Team Assembly and Execution → Integrated Report Generation
- Requests like write an incident postmortem
- SKILL.md covers Execution Mode, Agent Composition, Workflow and Modes by Task Scale, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Incident Postmortem is an agent skill from revfactory/harness-100. A full pipeline where an agent team collaborates to generate incident postmortem reports. Systematically performs timeline reconstruction, root cause analysis, impact assessment, and remediation planning. Use this skill for requests like 'write an incident postmortem', 'post-incident analysis report', 'create an incident report', 'incident report', 'root cause analysis', 'RCA report', 'organize incident timeline', 'establish remediation measures', and other incident analysis tasks. Note: real-time incident…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems, Root cause analysis and Incident response. The licence is Apache-2.0.
When your agent uses it
- Requests like write an incident postmortem
- Post-incident analysis report
- Create an incident report
- Incident report
Example prompts
- “write an incident postmortem”
- “post-incident analysis report”
- “create an incident report”
- “/incident-postmortem”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Incident Postmortem loads about 1.8k tokens when it runs. Until then it costs about 159 tokens; SKILL.md has 689 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 689 words, ~1,811 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-postmortem/SKILL.md (or your agent's skills folder).- name
- incident-postmortem
- description
- A full pipeline where an agent team collaborates to generate incident postmortem reports. Systematically performs timeline reconstruction, root cause analysis, impact assessment, and remediation planning. Use this skill for requests like 'write an incident postmortem', 'post-incident analysis report', 'create an incident report', 'incident report', 'root cause analysis', 'RCA report', 'organize incident timeline', 'establish remediation measures', and other incident analysis tasks. Note: real-time incident response (on-call), monitoring system setup, and alert configuration are outside the scope of this skill.
Incident Postmortem — Incident Post-Analysis Pipeline
An agent team collaborates to perform timeline reconstruction -> root cause analysis -> impact assessment -> remediation planning -> report generation.
Execution Mode
Agent Team — 5 members communicate directly via SendMessage and cross-validate each other.
Agent Composition
| Agent | File | Role | Type |
|---|---|---|---|
| timeline-reconstructor | .claude/agents/timeline-reconstructor.md | Event collection, chronological ordering, gap identification | general-purpose |
| root-cause-investigator | .claude/agents/root-cause-investigator.md | 5 Whys, Fishbone, Fault Tree | general-purpose |
| impact-assessor | .claude/agents/impact-assessor.md | User/revenue/SLA/reputation impact assessment | general-purpose |
| remediation-planner | .claude/agents/remediation-planner.md | Short/mid/long-term countermeasures, action items | general-purpose |
| postmortem-reviewer | .claude/agents/postmortem-reviewer.md | Cross-validation, blameless culture verification | general-purpose |
Workflow
Phase 1: Preparation (Performed directly by Orchestrator)
- Extract from user input:
- Incident Description: What happened and when
- Evidence (optional): Logs, metric screenshots, chat records, alert records
- Impact Information (optional): Number of affected users, services, duration
- Actions Taken (optional): Emergency measures already performed
- Create
_workspace/directory at the project root - Organize input and save to
_workspace/00_input.md - If existing files are available, copy them to
_workspace/and skip the corresponding Phase - Determine execution mode based on the scope of the request (see "Modes by Task Scale" below)
Phase 2: Team Assembly and Execution
| Order | Task | Assignee | Dependencies | Deliverable |
|---|---|---|---|---|
| 1 | Timeline Reconstruction | reconstructor | None | _workspace/01_timeline.md |
| 2a | Root Cause Analysis | investigator | Task 1 | _workspace/02_root_cause.md |
| 2b | Impact Assessment | assessor | Task 1 | _workspace/03_impact_assessment.md |
| 3 | Remediation Planning | planner | Tasks 2a, 2b | _workspace/04_remediation_plan.md |
| 4 | Final Review | reviewer | Tasks 1-3 | _workspace/05_review_report.md |
Tasks 2a (root cause) and 2b (impact) can be executed in parallel.
Inter-team Communication Flow:
- reconstructor completes -> delivers timeline and trigger candidates to investigator; delivers incident duration and metrics to assessor
- investigator completes -> delivers root cause and contributing factors to planner
- assessor completes -> delivers impact magnitude and SLA violation status to planner
- planner completes -> delivers full countermeasures to reviewer
- reviewer cross-validates all deliverables. Requests fixes for RED Must Fix items (up to 2 times)
Phase 3: Integrated Report Generation
- Generate
_workspace/postmortem_report.mdintegrating all deliverables - Report structure: Summary -> Timeline -> Root Cause -> Impact -> Remediation -> What Went Well -> Lessons Learned
- Deliver the final report to the user
Modes by Task Scale
| User Request Pattern | Execution Mode | Deployed Agents |
|---|---|---|
| "Write a postmortem report" | Full Pipeline | All 5 agents |
| "Organize the incident timeline" | Timeline Mode | reconstructor + reviewer |
| "Analyze the root cause" | RCA Mode | reconstructor + investigator + reviewer |
| "Just create remediation measures" (cause analysis exists) | Remediation Mode | planner + reviewer |
| "Review this postmortem" | Review Mode | reviewer only |
Leveraging Existing Files: If the user provides existing timelines, cause analyses, etc., copy the files to the appropriate location in _workspace/ and skip the corresponding agent's step.
Show full SKILL.md (283 more words)Show less
Data Transfer Protocol
| Strategy | Method | Purpose |
|---|---|---|
| File-based | _workspace/ directory | Store and share main deliverables |
| Message-based | SendMessage | Real-time delivery of key information, fix requests |
| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |
Error Handling
| Error Type | Strategy |
|---|---|
| Insufficient incident information | Ask user additional questions, tag uncertain parts with "[Unconfirmed]" |
| Logs/metrics inaccessible | Reconstruct from verbal accounts, tag with "[Verbal account-based]" |
| Agent failure | Retry once -> if fails, proceed without that deliverable, note omission in review |
| RED found in review | Request fix from relevant agent -> rework -> re-verify (up to 2 times) |
| Blaming language found | Reviewer immediately requests fix — blameless culture is an absolute principle |
Test Scenarios
Normal Flow
Prompt: "Yesterday at 2 PM the payment service was down for 30 minutes. It happened right after a deployment and was recovered by rollback. Create a postmortem report." Expected Result:
- Timeline: Deployment -> incident start -> detection -> response -> rollback -> recovery in chronological order
- Root Cause: Specific defect in deployed code, contributing factors like no canary deployment
- Impact: User count, revenue loss, SLA impact estimates
- Remediation: SMART action items like canary deployment adoption, auto-rollback, alert improvements
- Integrated Report: Complete postmortem ready for executive reporting
Existing File Utilization Flow
Prompt: "Review this postmortem report" + report attached Expected Result:
- Copy existing report to
_workspace/ - Execute in review mode
- Verify consistency, completeness, and blameless culture adherence
- Provide improvement suggestions
Error Flow
Prompt: "The API server was slow this morning. Analyze the cause." Expected Result:
- Collect incident details through additional questions (time, impact, actions, etc.)
- Execute RCA mode with collected information
- Clearly mark uncertain parts
Agent Extension Skills
| Skill | Path | Enhanced Agent | Role |
|---|---|---|---|
| rca-methodology | .claude/skills/rca-methodology/skill.md | root-cause-investigator | 5 Whys, Fishbone, Fault Tree, change analysis, cognitive bias prevention |
| sla-impact-calculator | .claude/skills/sla-impact-calculator/skill.md | impact-assessor | SLA/SLO/SLI framework, error budgets, revenue loss estimation, severity levels |
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/25-incident-postmortem/.claude/skills/incident-postmortem of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Incident Postmortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Incident Postmortem this skillrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 108 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Conducting Post Incident Lessons Learnedmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Incident Postmortemgithub/awesome-copilot | 40k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Incident Response Patternsvibeeval/vibecosystem | 531 | — | ~709 | Automated safety check: Pass | MIT | |
| Debug Production IssueFerroxLabs/wayland | 608 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Conducting Post Incident Lessons Learned
mukul975/Anthropic-Cybersecurity-Skills
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
- Official
Incident Postmortem
github/awesome-copilot
A skill your agent uses when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem.
Incident Response Patterns
vibeeval/vibecosystem
Incident severity classification, runbook templates, root cause analysis, and post-incident review
Debug Production Issue
FerroxLabs/wayland
Orchestrates systematic production debugging from alert through root cause identification and resolution, chaining four engineering skills into a structured diagnostic pipeline.
Incident Response Lifecycle
LeoYeAI/openclaw-master-skills
Incident response process management following the NIST 800-61 lifecycle.
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Incident Postmortem
What does Incident Postmortem do?
A full pipeline where an agent team collaborates to generate incident postmortem reports. Incident Postmortem is an agent skill from revfactory/harness-100. A full pipeline where an agent team collaborates to generate incident postmortem reports.
When should I use Incident Postmortem?
Incident Postmortem fits situations like: requests like write an incident postmortem; post-incident analysis report; create an incident report; incident report.
How do I install Incident Postmortem in Claude Code?
Run `npx skills add revfactory/harness-100 --skill incident-postmortem -a claude-code`. Or copy the skill folder (en/25-incident-postmortem/.claude/skills/incident-postmortem in revfactory/harness-100) into .claude/skills/incident-postmortem in your project. Claude Code loads it when a task matches its description.
How do I install Incident Postmortem in Codex?
Run `npx skills add revfactory/harness-100 --skill incident-postmortem -a codex`. Or copy the skill folder (en/25-incident-postmortem/.claude/skills/incident-postmortem in revfactory/harness-100) into .agents/skills/incident-postmortem in your project. Codex loads it when a task matches its description.
Can I use Incident Postmortem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill incident-postmortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-postmortem, .gemini/skills/incident-postmortem, .github/skills/incident-postmortem and .opencode/skills/incident-postmortem in your project.
What does Incident Postmortem need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Postmortem is instructions for the agent only.
Does Incident Postmortem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Incident Postmortem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Incident Postmortem use?
Incident Postmortem is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Incident Postmortem use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Incident Postmortem?
Skills that share tags, products or a category with Incident Postmortem: Post-Incident Debrief (VeryGoodOpenSource/vgv-wingspan, 108 stars), Conducting Post Incident Lessons Learned (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Incident Postmortem (github/awesome-copilot, 40k stars) and Incident Response Patterns (vibeeval/vibecosystem, 531 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Postmortem?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.