compound-docs

To document solved technical problems automatically, you can use a confirmation phrase or the /doc-fix command to capture the problem context, root cause, and solution from your conversation and generate a Markdown file.

Generating Markdown documentation with validated YAML frontmatter involves capturing the problem context and solution, validating the data against a YAML schema, and creating a categorized file with structured metadata for fast lookups.

The best way to build a searchable knowledge base from debugging sessions is to transform conversational solutions into categorized Markdown files with structured YAML frontmatter, enabling fast future reference and lookups.

Yes, you can organize code documentation into categorized directories based on problem type. The process automatically categorizes technical solutions into relevant directories such as performance-issues during file creation.

Yes, the automated documentation process supports optional cross-referencing and pattern promotion. It checks existing documentation before file creation to optionally link related solutions and promote recurring patterns.

You should not use an automated Markdown documentation generator when a problem remains unsolved or lacks a clear root cause, as the process specifically requires captured conversational solutions and validated context to generate useful entries.