compound-docs

Compound-docs captures solved problems as markdown files with YAML frontmatter after you confirm resolution. It categorizes documentation into directories, sanitizes filenames, and validates metadata against a schema for fast lookup and knowledge reuse across sessions.

Categories are enum-constrained in compound-docs to ensure consistent problem classification. The Skill generates one markdown file per solved issue under category directories (docs/solutions/[category]), enabling standardized organization across your knowledge base.

Yes. Compound-docs automatically stores solved problems as categorized markdown files with YAML frontmatter metadata, creating a deterministic, searchable knowledge base. Future sessions can retrieve solutions quickly by category and problem type.

YAML frontmatter in compound-docs stores structured metadata validated against a defined schema, enabling fast lookup by problem attributes. Frontmatter fields are extracted from Step 2 context and templated into each markdown file for efficient filtering and retrieval.

Compound-docs sanitizes filenames automatically to ensure deterministic file creation and safe filesystem compatibility. Original problem details are preserved in YAML frontmatter and markdown content while filenames remain clean and consistent.

Yes. Compound-docs categorizes solutions by problem type and environment through enum-constrained categorization, storing each solved issue as a separate markdown file. This supports diverse problem domains and contexts within a unified knowledge base.