compound-docs

To auto-document solved coding bugs into searchable Markdown files, this Skill captures confirmed solutions and organizes them into categorized Markdown files with YAML frontmatter for fast lookup. Each entry is stored within symptom-category directories like docs/solutions/performance-issues/.

Structured problem documentation requires YAML frontmatter fields including module, date, problem_type, component, symptoms, root_cause, and severity. These fields enable consistent categorization, cross-referencing, and rapid retrieval of proven solutions across your institutional knowledge base.

To create a searchable knowledge base from resolved software issues, this Skill automatically documents each confirmed solution as a distinct Markdown file using standardized templates. This builds a searchable repository of proven solutions categorized by symptom directories.

This automated documentation tool requires no external dependencies to operate. It relies solely on structured Markdown files and YAML frontmatter to store and organize resolved problems within your local repository structure.

The best way to standardize bug tracking documentation across a team is using standardized resolution templates. This Skill provides a consistent template via assets/resolution-template.md to ensure uniform documentation quality and structured frontmatter for every solved problem entry.

YAML frontmatter categorizes solved development problems by embedding structured metadata fields like problem_type and symptoms directly in Markdown files. This enables consistent categorization, fast lookup, and easy discovery of proven solutions within your institutional knowledge base.