compound-docs

Convert solved problems into categorized YAML-frontmatter markdown documentation.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/robwestz/bacowr_b --skill compound-docs-robwestz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/robwestz/bacowr_b/tree/main/every-marketplace/plugins/compound-engineering/skills/compound-docs
Command: npx skills add https://github.com/robwestz/bacowr_b --skill compound-docs-robwestz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill captures solved problem solutions as categorized documentation using YAML frontmatter to enable fast lookup and centralized knowledge.

Core Features & Use Cases

  • Template-driven documentation: Generates category-based, frontmatter-rich markdown files for each solved problem.
  • Category-based organization: Enforces enum-driven categorization and automated directory mapping for fast discovery.
  • Cross-reference & templating: Supports references to related issues, canonical templates, and asset-backed guidance.

Quick Start

Use the compound-docs skill to document a recently solved issue by following the 7-step workflow outlined in the skill body.

Frequently Asked Questions about compound-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically convert solved problems into searchable documentation?

Template-driven file generation converts solved problems into categorized markdown files with YAML frontmatter under a docs/solutions directory. This enforces schema validation and automates category-based organization for fast lookup.

What is YAML frontmatter used for in a knowledge base?

In a knowledge base, YAML frontmatter embeds metadata for category-based organization and fast lookup. It enables schema validation, cross-references, and centralized discovery of documented solutions.

How do I organize documentation by category using templates?

Apply enum-driven categorization and automated directory mapping to generate frontmatter-rich markdown files. This template-driven approach enforces schema validation and creates category-specific docs for fast discovery.

Can I add cross-references and assets to generated documentation files?

Yes, generated documentation files support cross-references and assets. The workflow includes references to related issues, canonical templates, and asset-backed guidance to provide comprehensive context for each solution.

Does schema validation enforce required fields in markdown documentation?

Schema validation enforces required fields and enum-driven categorization in markdown documentation. This ensures consistent YAML frontmatter, accurate directory mapping, and reliable cross-references across the knowledge base.

What is the best way to document a recently solved issue for future lookup?

Following a structured workflow that captures the solution as a categorized markdown file with YAML frontmatter is the best way to document a solved issue. This applies schema validation and template-driven generation for centralized knowledge.