compound-docs

Capture solved problems as categorized markdown documentation with YAML frontmatter.

461|129|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/davekilleen/Dex --skill compound-docs-davekilleen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/davekilleen/Dex/tree/main/.claude/plugins/compound-engineering/skills/compound-docs
Command: npx skills add https://github.com/davekilleen/Dex --skill compound-docs-davekilleen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automatically documents solved problems, transforming them into searchable institutional knowledge with structured YAML frontmatter for fast lookup and categorization.

Core Features & Use Cases

  • Automated Documentation: Captures problem solutions immediately after confirmation, creating structured markdown files.
  • Categorized Knowledge Base: Organizes documentation by symptom category (e.g., docs/solutions/performance-issues/).
  • YAML Frontmatter: Uses validated YAML for metadata, enabling robust search and discovery.
  • Use Case: After debugging a complex performance issue, this skill will automatically create a detailed markdown file in the performance-issues directory, complete with the root cause, solution, and relevant code snippets, making it easily discoverable for future reference.

Quick Start

Use the compound-docs skill to document a recently solved problem by saying "that worked".

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I automatically document solved debugging problems in markdown?

Automatically document solved debugging problems by capturing the context, root cause, and solution into structured markdown files. This creates a searchable knowledge base immediately after you confirm a fix.

Can I organize my knowledge base directories by symptom category using YAML frontmatter?

Yes, you can organize your knowledge base directories by symptom category using validated YAML frontmatter. This approach structures files into folders like performance-issues, enabling robust search and fast discovery.

What's the best way to trigger automated documentation after fixing a code issue?

Trigger automated documentation after fixing a code issue by manually invoking /doc-fix or using auto-detection. Simply saying "that worked" captures the solution and categorizes it into your institutional knowledge base.

Does this problem solving documentation approach require external dependencies?

No external dependencies are required for this problem solving documentation approach. It operates independently to extract context, validate metadata against a schema, and generate categorized markdown files.

How does schema validation work for YAML frontmatter in a categorized knowledge base?

Schema validation for YAML frontmatter in a categorized knowledge base works by extracting problem-solving context and validating it against a predefined structure. This ensures metadata consistency for robust search and lookup across symptom-based directories.