skills.rest
roach88
roach88COMMUNITY
Explore all skills by this author →
GitHub

compound-docs

Document solved problems into categorized knowledge bases with YAML frontmatter.

3|Updated Feb 5, 2026
Search Tags:#automation#documentation#yaml-frontmatter#knowledge-base#docs-solutions#category-catalog
One-click install
npx skills add https://github.com/roach88/compound-engineering --skill compound-docs-roach88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/roach88/compound-engineering/tree/main/skills/compound-docs
Command: npx skills add https://github.com/roach88/compound-engineering --skill compound-docs-roach88

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Documentation of solved problems is standardized and organized, enabling fast lookup and knowledge reuse across teams.

Core Features & Use Cases

  • Automatically capture and store solved problem details with YAML frontmatter for consistency.
  • Organize each solution into category-based directories (docs/solutions/[category]/...).
  • Enforce a strict frontmatter schema to ensure searchable, machine-readable metadata and cross-references.

Quick Start

Provide a confirmed solution and run the documentation capture workflow to generate a categorized docs file under 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 organize solved engineering problems into a categorized knowledge base?▼

To organize solved problems into a knowledge base, this Skill captures each solution with YAML frontmatter and stores it in category-based directories under docs/solutions for fast lookup and reuse.

How do I document code changes with YAML frontmatter for future reuse?▼

Documenting code changes with YAML frontmatter involves applying a strict schema that enforces enum values and preserves detailed context, ensuring machine-readable metadata and cross-references for future reuse.

What's the best way to standardize documentation across engineering and product teams?▼

Standardizing documentation across teams is achieved by enforcing a strict frontmatter schema with enum values, automatically categorizing each confirmed solution into directories for consistent cross-team lookup.

Does this documentation workflow require any dependencies or setup?▼

This documentation workflow requires no external dependencies, operating independently to generate categorized docs files and apply the strict frontmatter schema directly within your environment.

When should I use category-based directories for storing solution documentation?▼

Category-based directories for solution documentation should be used when you need to standardize solved problem details and enable fast lookup across engineering and product contexts for knowledge reuse.

Related Skills

Explore More Content & Communication Skills→
All-The-VibesAll-The-Vibes
50

compound-docs

Document solved problems as categorized YAML-frontmatter markdown files.

Official
Advanced
giraphantgiraphant
2

quasi:synthesize

Generate cross-text synthesis reports, aggregated reference lists, and knowledge base updates from analysis files.

Community
Advanced
windyskywindysky

moai-docs-generation

Generate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.

Community
Advanced
hollandkevinthollandkevint
5

compound-docs

Capture solved technical problems into categorized Markdown files with YAML frontmatter.

Community
Advanced