compound-docs

Document solved problems with YAML frontmatter by triggering a templated workflow that generates a single markdown file per incident, capturing context, solutions, and cross-references for fast knowledge retrieval.

Structured documentation for incidents should include frontmatter fields like module, date, problem_type, component, symptoms, root_cause, resolution_type, and severity, with optional rails_version and tags to improve discoverability.

Organize solution documentation into a categorized knowledge base by applying a category-based file structure under docs/solutions, writing a single markdown file per incident with enum-validated problem types and metadata.

Create a repeatable documentation workflow for resolved issues by applying templates that enforce enum-validated metadata and cross-references, ensuring a single markdown entry is written per incident after validation.

No external dependencies are required to generate YAML-frontmatter structured notes; the workflow operates independently to write categorized markdown files with validated metadata fields for each solved problem.

Yes, you can add tags and optional framework versions like rails_version to categorized solution docs, alongside required frontmatter fields including module, problem_type, symptoms, and root_cause for complete knowledge records.