compound-docs

Capture solved technical problems into Markdown knowledge base entries with YAML frontmatter.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/hemory/amp --skill compound-docs-hemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/hemory/amp/tree/main/.claude/plugins/compound-engineering/skills/compound-docs
Command: npx skills add https://github.com/hemory/amp --skill compound-docs-hemory

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of documenting solved technical problems, turning them into searchable knowledge base entries to prevent future occurrences and accelerate team learning.

Core Features & Use Cases

  • Automatic Documentation: Captures problem context, root cause, and solution after confirmation.
  • Structured Knowledge Base: Creates categorized Markdown files with YAML frontmatter for easy searching and retrieval.
  • Use Case: After debugging a complex performance issue, invoke this skill to automatically generate a detailed documentation entry in the docs/solutions/performance-issues/ directory, complete with error messages, investigation steps, and the fix.

Quick Start

Use the compound-docs skill to document the solution to the recent database connection error.

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 technical problems automatically?

To document solved technical problems automatically, this Skill extracts context, root cause, and solution details from conversation history and generates categorized Markdown knowledge base entries with validated YAML frontmatter.

How do I structure a technical knowledge base using Markdown and YAML?

You can structure a technical knowledge base using Markdown files with YAML frontmatter, organizing entries by problem type and component to enable easy searching and retrieval of documented solutions.

Can I capture debugging context and root cause details after fixing an issue?

Yes, you can capture debugging context and root cause details immediately after fixing an issue, as this Skill automates the extraction of investigation steps and error messages from conversation history upon confirmation.

What is the best way to create searchable documentation for recurring software issues?

The best way to create searchable documentation for recurring software issues is to automate the extraction of problem context and solution details into categorized Markdown files with structured YAML frontmatter for immediate retrieval.

Does this knowledge base tool support cross-referencing and pattern detection?

Yes, this knowledge base tool supports optional cross-referencing and pattern detection, allowing you to link related technical problems and identify recurring issues across categorized Markdown documentation.

How do I categorize technical writing entries by problem type and component?

You can categorize technical writing entries by problem type and component through the automated generation of Markdown files in structured directory paths, ensuring validated YAML frontmatter captures the specific component metadata.