compound-docs

Documenting solved problems as categorized markdown files with YAML frontmatter enables searchable knowledge base retrieval. This approach stores records under docs/solutions/[category]/ directories, applying structured metadata schemas and cross-references for fast lookup and navigation.

To create documentation with YAML frontmatter, trigger the skill after a problem is solved. It uses a resolution-template to generate one markdown file per issue, enforcing a YAML schema to validate metadata structure and storing it under docs/solutions/[category]/ for consistent organization.

Yes, you can organize markdown documentation by category and add cross-references. The skill automatically stores generated docs under docs/solutions/[category]/ directories and applies cross-references, ensuring categorized documentation remains navigable and interconnected across the knowledge base.

Yes, you need file write permissions to generate searchable docs. The skill requires the ability to write files and create directories under docs/solutions/ to persist resolved tickets as categorized markdown documentation with validated YAML frontmatter.

You should avoid template-based knowledge base documentation when a problem lacks a verified resolution or when the issue does not require a repeatable, searchable record. The skill strictly applies after a problem is solved and needs structured persistence with YAML frontmatter.