compound-docs

Document solved problems by automatically generating categorized, YAML-frontmatter files under docs/solutions/[category]/ to enable structured metadata and fast retrieval. Each issue is saved as a single, category-labeled file immediately after solution confirmation.

You need YAML frontmatter for your troubleshooting knowledge base when you want to enforce structured metadata, apply category mapping, and establish cross-references to support efficient retrieval and analytics across your documented solutions.

The best way to organize troubleshooting documentation is using a single-file-per-issue approach, storing records under docs/solutions/[category]/[filename] to maintain clear categorization and keep documentation concise and navigable for onboarding.

No, this documentation approach does not require manual categorization for every solved issue. It automatically maps symptoms to categories and generates the structured file with cross-references immediately after you confirm a solution.

Cross-references in a single-file-per-issue knowledge base work by embedding links within the YAML frontmatter metadata. This connects related troubleshooting documents across different category directories to support quick lookup and knowledge sharing.