compound-docs

Automated documentation of solved problems captures problem context, root cause, and solution directly from conversations. It processes the discussion context and transforms conversational solutions into searchable knowledge base entries.

Creating a searchable knowledge base from solved issues involves organizing documentation into categorized files with YAML frontmatter. This structure validates against a schema and organizes files by problem type for fast lookup.

YAML frontmatter helps document technical solutions by providing structured metadata for fast lookup. It validates entries against a schema, enabling quick search and retrieval of categorized problem-solving context.

You can automatically organize documentation into categorized files after fixing a bug. The skill processes the conversation context and places the generated markdown file in the appropriate problem type category.

A schema is used to validate documented problem solutions, ensuring the YAML frontmatter and captured context meet structured requirements. This validation step maintains consistency across the institutional knowledge base.

Automated problem documentation is not suited for incomplete or unresolved technical issues. It requires a fully solved problem with clear context, root cause, and solution to generate accurate, categorized knowledge base entries.