timequity/postmortem-writing
skills/postmortem-writing/SKILL.md
Document root cause analysis for team learning. Blameless, actionable, preventive.
documentation
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add timequity/vibe-coder postmortem-writingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 8:22 AM4.6s1 file scanned
SKILL.md
- name:
- postmortem-writing
- description:
- Document root cause analysis for team learning. Blameless, actionable, preventive.
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
Related Skills
timequity/verification-gate
development
VerifiedTrustedCommunity
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
SKILL.mdUpdated Apr 17, 2026
timequity/verification-before-completion
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete or fixed - requires running verification commands and confirming output before making any success claims
SKILL.mdUpdated Apr 17, 2026
timequity/ui-generator
tools
VerifiedTrustedCommunity
Generate UI components from natural language descriptions. Use when: user asks for a page, component, or UI element. Triggers: "create page", "add component", "show form", "make button", "страница", "компонент", "форма".
SKILL.mdUpdated Apr 17, 2026
timequity/theme-factory
content-media
VerifiedTrustedCommunity
10 ready-to-use themes with colors and fonts for consistent styling. Use when: applying visual themes to pages, components, or design systems. Triggers: "theme", "color palette", "color scheme", "fonts", "branding", "visual identity", "design system colors".
SKILL.mdUpdated Apr 17, 2026