compound-docs

Generate categorized markdown solution docs with validated YAML frontmatter.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ollieb89/orchestrator --skill compound-docs-ollieb89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/ollieb89/orchestrator/tree/main/.cursor/skills/compound-docs
Command: npx skills add https://github.com/ollieb89/orchestrator --skill compound-docs-ollieb89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures solved problems as categorized documentation with YAML frontmatter to enable fast lookup in a centralized knowledge base.

Core Features & Use Cases

  • Automatically generate a structured documentation file for each solved problem immediately after confirmation.
  • Organize files into category-specific directories under docs/solutions with a consistent YAML frontmatter schema for quick search and reference.
  • Provide cross-reference and pattern-detection workflows for broader knowledge capture.

Quick Start

After a solution is confirmed, generate a categorized markdown doc under docs/solutions that includes the YAML frontmatter and detailed solution context.

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

You can document solved problems by generating categorized markdown files with YAML frontmatter under a docs/solutions directory. This workflow validates the frontmatter against a schema to ensure consistent metadata for fast lookup and reference.

What is the best way to organize documentation files by category?▼

Organize documentation files by placing them into category-specific directories under docs/solutions. This structure uses a consistent YAML frontmatter schema to enable quick search and centralized knowledge base discovery.

How do I validate YAML frontmatter against a schema for markdown docs?▼

Validating YAML frontmatter is handled automatically by checking the generated markdown entries against a predefined schema.yaml. This ensures the metadata conforms to the established structure before the document is populated with context.

Does this documentation workflow require any external dependencies to run?▼

No external dependencies are required to run this documentation workflow. The process operates independently to validate frontmatter, create the directory structure, and populate the markdown template with solution context.

When should I generate a markdown documentation file for a problem?▼

Generate a markdown documentation file immediately after a solution is confirmed. This ensures the solved problem is captured with detailed context and organized properly before the information is lost.

Can I use shared templates to populate solution documentation automatically?▼

Yes, shared templates and assets are used to populate the document with context automatically. This ensures every generated markdown entry maintains a consistent format aligned with the YAML frontmatter schema.