compound-docs

To document solved problems into a searchable knowledge base, this Skill captures conversation context after issue resolution and generates structured Markdown files with YAML frontmatter. Each solved problem is stored as an individual file under a specific category directory for fast lookup and discovery.

YAML frontmatter provides structured metadata at the top of Markdown documentation files to support indexing and quick discovery. This Skill enforces a consistent frontmatter schema defined in a configuration file, ensuring every categorized knowledge base entry remains uniformly searchable.

To organize troubleshooting documentation by category automatically, this Skill maps solved problems to category directories such as performance-issues or reliability-issues. It creates one Markdown file per problem, placing it in the correct category folder based on the analyzed problem context.

You do not need to manually trigger documentation generation independently. This Skill operates across post-confirmation contexts, meaning you confirm the problem is solved and it automatically generates the categorized Markdown file with the appropriate YAML frontmatter directly from the conversation context.

You can customize the YAML frontmatter schema for your categorized docs by modifying the schema configuration file. The Skill uses this defined schema and a provided frontmatter template to enforce consistent metadata structure across all generated Markdown documentation files in the knowledge base.

The best way to create a knowledge base from resolved support tickets is using automated documentation categorization. This Skill captures the resolved issue context, maps it to a category directory, and outputs a Markdown file with standardized YAML frontmatter for immediate searchability and retrieval.