ReddRadar
Agent skill
postmortem-writing
Document root cause analysis for team learning. Blameless, actionable, preventive.
Install this agent skill to your Project
npx add-skill https://github.com/timequity/vibe-coder/tree/main/skills/postmortem-writing
SKILL.md
Postmortem Writing
Purpose
- Share learnings across team
- Prevent recurrence
- Build institutional knowledge
- Blameless culture
Template
# Postmortem: [Incident Title]
**Date:** YYYY-MM-DD
**Duration:** X hours
**Severity:** P1/P2/P3
**Author:** [Name]
## Summary
One paragraph describing what happened and impact.
## Timeline
- HH:MM - Event
- HH:MM - Detection
- HH:MM - Response started
- HH:MM - Mitigation
- HH:MM - Resolution
## Root Cause
Technical explanation of why this happened.
Use 5 Whys technique if helpful.
## Impact
- Users affected: X
- Revenue impact: $Y
- Data loss: None/Partial/Full
## What Went Well
- Detection was fast
- Team responded quickly
- Communication was clear
## What Went Wrong
- Monitoring gap
- Missing validation
- Unclear runbook
## Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| Add monitoring for X | @person | YYYY-MM-DD |
| Implement validation | @person | YYYY-MM-DD |
| Update runbook | @person | YYYY-MM-DD |
## Lessons Learned
Key takeaways for the team.
Principles
Blameless
- Focus on systems, not people
- "The system allowed X" not "Person did X"
- Assume good intentions
Actionable
- Every finding has an action item
- Actions have owners and dates
- Follow up on completion
Honest
- Don't minimize impact
- Include what went wrong
- Acknowledge gaps
5 Whys Example
- Why did the query fail? → Null user_id
- Why was user_id null? → Auth didn't set it
- Why didn't auth set it? → Token was expired
- Why wasn't expiry handled? → Missing check
- Why was check missing? → No test coverage
Root cause: Missing test for token expiry path
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
timequity/vibe-coder
mvp-help
Help and documentation for Idea to MVP plugin. Use when: user asks about building MVPs, vibe coding, or available commands. Triggers: "help", "what can you do", "mvp help", "how to build".
timequity/vibe-coder
verification-gate
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
timequity/vibe-coder
brainstorming
Refine ideas into detailed designs through Socratic dialogue. Use when: user has rough idea, needs to clarify requirements, explore approaches. Triggers: "brainstorm", "discuss idea", "I'm thinking about", "what if", "help me think through", "explore options", "/brainstorm".
timequity/vibe-coder
subagent-creator
Guide for creating effective subagents (custom agents). Use when users want to create a new subagent that can be dispatched via Task tool for autonomous work. Covers frontmatter fields (name, description, tools, model, permissionMode, skills), prompt design, and when to use subagents vs skills.
timequity/vibe-coder
backend-rust
Modern Rust backend with Axum, SQLx, tokio + CI/CD automation. Use when: building Rust APIs, high-performance services, or needing build/test/lint/audit automation. Triggers: "axum", "rust backend", "rust api", "sqlx", "tokio", "cargo build", "cargo test", "clippy", "rustfmt", "cargo-audit", "cross-compile", "rust ci", "release build", "rust security", "shuttle", "actix".
timequity/vibe-coder
test-driven-development
Write failing test first, then minimal code to pass. Red-Green-Refactor cycle. Use when: implementing features, fixing bugs, refactoring code. Triggers: "implement", "add feature", "fix bug", "tdd", "test first", "write tests", "test-driven".
Didn't find tool you were looking for?