compound-docs

Document solved problems into categorized YAML-frontmatter markdown notes.

11|Updated Mar 1, 2026

Search Tags:#templates #documentation #yaml-frontmatter #knowledge-base #cross-reference #documentation-workflow

Ready to run

npx skills add https://github.com/abuiles/agents-kanban --skill compound-docs-abuiles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/abuiles/agents-kanban/tree/main/.agents/skills/compound-docs
Command: npx skills add https://github.com/abuiles/agents-kanban --skill compound-docs-abuiles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Automatically document solved problems into categorized, YAML-frontmatter based docs to enable fast lookup and knowledge reuse.

Core Features & Use Cases

Create a structured, searchable record for each solved problem using category directories and YAML frontmatter
Enforce enum-validated problem types and metadata to improve discoverability
Provide a repeatable documentation flow after validation, including templates and cross-references

Quick Start

Save a documented solution by triggering the compound-docs workflow to generate a YAML-frontmatter markdown entry in docs/solutions.

Frequently Asked Questions about compound-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document solved problems with YAML frontmatter for knowledge retrieval?▼

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.

What metadata fields should I include when creating structured documentation for incidents?▼

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.

How do I organize solution documentation into a categorized knowledge base?▼

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.

What's the best way to create a repeatable documentation workflow for resolved issues?▼

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.

Do I need any dependencies to generate YAML-frontmatter structured notes?▼

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.

Can I add tags and framework versions to my categorized solution docs?▼

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.