compound-docs

Automating documentation for solved problems involves capturing context, root cause, and solution metadata into YAML frontmatter. This process generates a single Markdown file per issue, storing it under a category derived from the problem type for a searchable knowledge base.

Organizing resolution docs into a categorized knowledge base is achieved by storing each Markdown file under docs/solutions/<category>. The category is automatically derived from the problem type, ensuring standardized and searchable records across the documentation.

Using Markdown templates for consistent documentation requires placing a template in assets/resolution-template.md. The system applies this template after solution confirmation to format entries, ensuring every documented issue follows the same structure.

You need a schema to validate YAML frontmatter for docs automation. The process validates the generated frontmatter against a schema.yaml file, ensuring standardized metadata fields are present before storing the Markdown doc in the knowledge base.

You should generate categorized documentation for a resolved issue immediately after confirming the solution. Running the process at this point captures the context and metadata accurately, creating a permanent record in the solutions directory.