Menu
Produce blameless postmortem and actionable follow-up backlog from incident artifacts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Initialize Flowbit with intelligent project analysis and documentation generation
Creates Mermaid diagrams for planning flows, component communication, and architecture views with adaptive detail selection (including C4 levels). This skill should be used when the user asks for a workflow, interaction, or architecture visualization from provided task context.
Internal engine for managing project documentation and technical standards in .flowbit/docs/. Handles file operations, INDEX.md generation, and .github/copilot-instructions.md integration. Invoked by flowbit-init, standards-update, and standards-discover skills.
Quick bug fix with TDD red/green gates and complexity escalation
Implement task directly with AI SDLC standards awareness (no planning mode)
Enter planning mode with AI SDLC standards awareness
| name | incident-postmortem |
| description | Produce blameless postmortem and actionable follow-up backlog from incident artifacts. |
| user-invocable | false |
Generate closure artifacts after mitigation and verification are complete.
| Parameter | Required | Description |
|---|---|---|
task_path | Yes | Absolute path to incident task directory |
verification_status | Yes | Stabilization verdict from verification phase |
Read:
{task_path}/analysis/incident-brief.md{task_path}/analysis/timeline.md{task_path}/analysis/hypotheses.md{task_path}/implementation/execution-log.md{task_path}/verification/incident-verification.mdCall Task tool:
flowbit-postmortem-authorSubagent output must include:
Create:
{task_path}/documentation/postmortem.md{task_path}/documentation/followups.mdstatus: success|partial|failed
postmortem_path: documentation/postmortem.md
followups_path: documentation/followups.md
followup_count: 0
Use blameless language. Follow-ups must be concrete, owner-ready tasks with acceptance signals.