compound-docs

Capture engineering solutions by drafting a markdown file with sections for Problem, Root Cause, Solution, Key Insight, and References. The file is saved under docs/learnings/<category>/ so future teams can review and avoid repeating the same investigation.

The best way to capture lessons learned is by proposing a concise postmortem document with standardized sections for Problem, Root Cause, and Solution. It requires your approval before saving, ensuring only verified workarounds are stored in your knowledge base.

Avoid duplicate documentation by checking existing entries before saving new learnings. The workflow identifies matching records, updates existing entries when appropriate, and flags recurring patterns to suggest broader skill updates rather than creating redundant files.

Yes, you can automate knowledge capture for deployment and configuration issues. The workflow detects trigger phrases like 'finally figured it out' during or after investigations, automatically drafting a proposed lesson learned document for your review and approval before saving.

Create a postmortem document when a fix requires investigation or a workaround, specifically after resolving debugging, configuration, integration, performance, testing, or deployment issues. This ensures hard-won insights are captured rather than lost as ad hoc notes.