compound-docs

Document solved problems as categorized entries with YAML frontmatter metadata.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill compound-docs-marchatton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/07-compound/compound-docs
Command: npx skills add https://github.com/marchatton/agent-skills --skill compound-docs-marchatton

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 searchable, categorized knowledge base entries to prevent future re-work and accelerate learning.

Core Features & Use Cases

  • Structured Documentation: Captures problem context, root cause, solution, and prevention steps in a standardized format.
  • Categorization & Searchability: Organizes documented issues by type and component, enabling fast lookups.
  • Use Case: After debugging a complex performance issue in the Rails model layer, use this Skill to create a detailed entry that includes the exact error, the fix, and preventative measures, making it easily discoverable for future similar problems.

Quick Start

Use the compound-docs skill to document the recent fix for the N+1 query issue in the Brief System.

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 debugging problems for future reference?

You can document solved debugging problems by capturing the context, root cause, solution, and prevention steps in a standardized format with YAML frontmatter, creating categorized knowledge base entries for fast lookup.

What is the best way to create a searchable knowledge base from troubleshooting fixes?

Creating a searchable knowledge base from troubleshooting fixes involves categorizing documented issues by type and component with YAML schema validation, enabling fast lookups to prevent future re-work.

Can I automate documentation creation when fixing a code issue?

Yes, you can automate documentation creation when fixing a code issue through confirmation phrases or manual invocation, which executes a structured 7-step workflow including filename generation and cross-referencing.

Does this problem solving documentation process check for existing entries before creating a new file?

Yes, the problem solving documentation process checks for existing documentation entries during its 7-step workflow to avoid duplicates before proceeding to filename generation, YAML schema validation, and cross-referencing.

What structure does the YAML frontmatter use for categorizing resolved issues?

The YAML frontmatter uses validated schemas to categorize documented issues by type and component, ensuring captured problem context and root cause details are organized for fast discovery and cross-referencing.