skills/postmortem/SKILL.md
Write blameless postmortems for significant bugs. Use after a bug fix to capture lessons learned.
npx skillsauth add the-own-lab/Claude-company-of-one postmortemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write blameless postmortems to capture lessons learned from significant bugs.
Chronological account of the incident:
Clear explanation of why the bug occurred. Link to the root cause analysis (DIAGNOSIS.md) if one was produced.
What was changed and why:
What this incident teaches about the codebase, process, or tooling:
Concrete preventive measures to reduce the likelihood of recurrence:
Read the template before producing the postmortem:
Read ${CLAUDE_PLUGIN_ROOT}/templates/POSTMORTEM.md
Link postmortem findings to the learn skill for pattern extraction. Patterns identified in postmortems should feed into the project's learning system to improve future pipeline runs.
documentation
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
development
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
documentation
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
content-media
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.