What problem does it solve? Solved debugging sessions and non-trivial fixes are often lost once a conversation ends, forcing teams to re-investigate the same issues. This Skill turns confirmed solutions into structured, searchable documentation so institutional knowledge accumulates instead of evaporating. ## Core Features & Use Cases - Automatic capture on confirmation: Detects phrases like "that worked" or "it's fixed" and documents the solution while context is fresh. - Schema-validated frontmatter: Every doc is validated against schema.yaml with enum-checked fields (problem_type, component, root_cause, severity) before any file is written. - Category-based organization: Files are routed into docs/solutions/ subdirectories (e.g., performance-issues, build-errors) with sanitized, dated filenames. - Cross-referencing and pattern promotion: Links related issues and can promote recurring critical patterns into a Required Reading file for all subagents. - Use Case: After fixing an N+1 query in a Rails Brief System, the skill creates docs/solutions/performance-issues/n-plus-one-brief-generation-BriefSystem-20251110.md with validated metadata, code examples, and prevention guidance. ## Quick Start After confirming a fix worked, ask the agent to document this solution using the compound-docs skill.
