compound-docs

Convert solved problems into categorized markdown docs with YAML frontmatter.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill compound-docs-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/compound-docs
Command: npx skills add https://github.com/drhazemibclc/plate --skill compound-docs-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automatically document solved problems into categorized, YAML-frontmatter-based markdown files to enable fast lookup and knowledge reuse.

Core Features & Use Cases

  • Structured documentation using YAML frontmatter for searchability
  • Organization into category directories by problem type to support scalable knowledge bases
  • Immediate generation of a reusable knowledge artifact after confirmation

Quick Start

Document the latest solved issue using the built-in documentation pipeline.

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 engineering problems into searchable documentation?

Generate YAML frontmatter documentation by applying a validated frontmatter schema against captured problem data. The workflow requires this schema to organize the module name, symptom, root cause, and solution fields into structured markdown files under docs/solutions/<category>/ for reliable knowledge base generation.

How does YAML frontmatter improve engineering knowledge base searchability?

YAML frontmatter improves knowledge base searchability by structuring solved problem details into validated metadata fields like module name, symptom, and root cause. This enables fast lookup and category-organized documentation across docs/solutions/<category>/ directories.

What is the best way to structure an engineering workflow for capturing problem-solution knowledge?

The best way to structure problem-solution knowledge capture is a templates-driven doc generation workflow that organizes files into docs/solutions/<category>/ directories. This applies after problem confirmation, capturing the module name, symptom, root cause, and solution into validated YAML frontmatter for scalable knowledge bases.

Do I need a frontmatter schema before generating docs from solved problems?

Yes, you need a frontmatter schema and a templates-driven doc generation workflow before generating docs. The schema validates the captured module name, symptom, root cause, and solution fields to ensure the generated markdown files under docs/solutions/<category>/ remain searchable and structured.