compound-docs

Document solved problems as categorized Markdown files with YAML frontmatter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/isndotbiz/ged --skill compound-docs-isndotbiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/isndotbiz/ged/tree/main/.claude/skills/compound-docs
Command: npx skills add https://github.com/isndotbiz/ged --skill compound-docs-isndotbiz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automatically captures delivered solutions and stores them as categorized Markdown documents with YAML frontmatter, creating a fast, searchable institutional knowledge base.

Core Features & Use Cases

  • Automatic documentation after problem confirmation, ensuring no solutions are lost.
  • Categorized docs organized under docs/solutions with category mapping for quick retrieval.
  • Uses YAML frontmatter for metadata and a minimal template in assets to maintain consistency across entries.
  • Supports cross-referencing related issues and reusing templates for rapid onboarding of new solutions.

Quick Start

After you confirm a solution, run the compound-docs workflow to generate a categorized docs 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 automatically document solved problems into a searchable knowledge base?

You can use YAML frontmatter in Markdown files to map categories, add descriptions, and include optional tooling references, ensuring your documentation remains structured and searchable across a knowledge base.

How do I create consistent documentation templates for a knowledge base?

You can establish consistent documentation by applying a minimal template from assets that standardizes YAML frontmatter fields such as name, description, and category mapping across all new solution entries.

Does automatic problem documentation require external dependencies to organize files?

No external dependencies are needed; the system uses internal components like references and assets to organize solution files under appropriate categories within the docs/solutions directory structure.

What is the best way to capture delivered solutions without losing institutional knowledge?

The best way to capture solutions is running an automated workflow after problem confirmation that generates categorized Markdown documents with YAML frontmatter, preventing institutional knowledge loss.