compound-docs

Extract context, root cause, and solutions from conversations into categorized YAML documentation.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/danfrdn/antigravity-config --skill compound-docs-danfrdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/danfrdn/antigravity-config/tree/main/skills/compound-docs
Command: npx skills add https://github.com/danfrdn/antigravity-config --skill compound-docs-danfrdn

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 problems, transforming them into a searchable knowledge base to prevent recurring issues and accelerate future problem-solving.

Core Features & Use Cases

  • Automated Documentation: Captures context, root cause, and solutions from conversations.
  • Structured Knowledge Base: Organizes documented solutions into categorized directories with validated YAML frontmatter for fast lookup.
  • Use Case: After fixing a complex bug, this skill automatically creates a detailed markdown file in docs/solutions/performance-issues/ with all relevant context, ensuring the fix and its reasoning are preserved for future reference.

Quick Start

Use the /doc-fix command after a problem has been solved to initiate documentation.

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 problems into a searchable knowledge base?

You can automatically document solved problems by using the /doc-fix command after a problem is resolved, which extracts context, root cause, and solutions from conversation history into structured markdown files.

How does YAML frontmatter validation work for institutional memory documentation?

YAML frontmatter validation works by checking extracted problem-solving context against a predefined schema, ensuring categorized documentation maintains consistent metadata for fast lookup and cross-referencing in the knowledge base.

What's the best way to organize debugging solutions for cross-referencing and pattern detection?

The best way to organize debugging solutions is categorizing them into structured `docs/solutions/` directories with validated YAML frontmatter, enabling automated cross-referencing and pattern detection for institutional learning.

Can I use this automated problem solving documentation tool without any external dependencies?

Yes, you can use this tool without any external dependencies. It operates independently using built-in scripts, references, and assets to extract context and validate YAML schemas for your knowledge base.

When do I need to capture conversation history for institutional learning?

You need to capture conversation history for institutional learning immediately after fixing complex bugs or resolving performance issues, ensuring the root cause, context, and solution reasoning are preserved before details are lost.