troubleshooting-doc

Documenting troubleshooting experiences involves recording structured knowledge into centralized docs. Using standardized templates for incident documentation captures evidence, root-cause analysis, actions, and prevention steps to enable rapid learning and reuse.

Structure a post-incident review by using phase-based prompts to capture evidence, root-cause analysis, actions, and prevention. Save the documented troubleshooting entry into a centralized docs directory to build a searchable incident management knowledge base.

You need an incident documentation template after complex debugging sessions, bug investigations, or resolved incidents. Auto-triggering template creation ensures critical troubleshooting knowledge is captured for future reference and recurrence avoidance.

Yes, this postmortem approach requires no external dependencies. It functions by writing a YAML frontmatter with name and description in SKILL.md, optionally referencing local directories for scripts, references, and assets to support on-demand troubleshooting resources.

Organize postmortem templates by saving structured troubleshooting entries under a centralized docs directory. Maintain an index within this directory to surface past problems, enabling fast retrieval and reuse of documented incident management knowledge.