What problem does it solve?
Engineering teams lose hours of productivity re-debugging issues that were already solved but never documented, as institutional knowledge is tied to individual conversation history instead of a shared, searchable knowledge base.
Core Features & Use Cases
- Validated Structured Documentation: Automatically generates categorized problem docs with strict YAML frontmatter validation against enum schemas for problem type, component, root cause, and severity, ensuring consistent, searchable records.
- 7-Step Capture Workflow: Guides users through confirmation detection, context gathering, duplicate doc checking, filename generation, validation gating, file creation, and cross-referencing for non-trivial solved problems.
- Critical Pattern Promotion: Identifies common, high-severity issues and lets users promote them to required reading for team-wide enforcement, preventing repeated mistakes.
Use case: After your team fixes a tricky N+1 query bug in the Brief System, this skill automatically creates a categorized, searchable doc with all context, error messages, and the fix, so no one else has to spend hours debugging the same issue.
Quick Start
Use the compound-docs skill to document the N+1 query issue we just fixed in the Brief System.