skills.rest
mengblom
mengblomCOMMUNITY
Explore all skills by this author →
GitHub

compound-docs

Convert confirmed solved problems into schema-validated markdown documentation.

Updated Aug 23, 2026
Search Tags:#documentation#troubleshooting#root cause analysis#knowledge base#schema validation#YAML frontmatter#debugging workflow
One-click install
npx skills add https://github.com/mengblom/dex-ghx --skill compound-docs-mengblom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/mengblom/dex-ghx/tree/main/.claude/plugins/compound-engineering/skills/compound-docs
Command: npx skills add https://github.com/mengblom/dex-ghx --skill compound-docs-mengblom

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It captures solved problems as structured, categorized documentation so future work can be faster and more consistent.

Core Features & Use Cases

  • Post-fix documentation capture: Automatically documents solutions after confirmation phrases (or via a manual /doc-fix trigger) to prevent knowledge loss.
  • Schema-validated resolution docs: Enforces YAML frontmatter with enum validation to keep documentation consistent and discoverable.
  • Searchable, category-based library: Creates one markdown doc per solved issue under a symptom/problem category for fast lookup and reuse.

Quick Start

Tell your AI that the issue is fixed (e.g., “that worked”), then ensure the conversation includes the module, exact symptoms/error message, stage, and the resolution steps so documentation can be generated and saved.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I automatically document debugging resolutions and root cause analysis?▼

You can automatically document debugging resolutions by confirming a fix in conversation or triggering a manual command, which captures the root cause analysis and resolution steps into a structured markdown file for future retrieval.

What is schema-validated documentation for troubleshooting workflows?▼

Schema-validated documentation for troubleshooting workflows enforces YAML frontmatter with enum validation on resolution docs, ensuring every captured fix remains consistently categorized and immediately discoverable in a searchable knowledge base.

Does this documentation workflow require YAML frontmatter for knowledge base entries?▼

Yes, this documentation workflow requires YAML frontmatter validated against a schema to ensure each troubleshooting resolution entry is properly categorized and structured for fast future lookup.

What's the best way to capture post-fix documentation for investigation workflows?▼

The best way to capture post-fix documentation for investigation workflows is to confirm the issue is fixed, ensuring the conversation includes the root cause analysis, prevention guidance, and verified fixes for deterministic doc creation.

When should I not use automated resolution docs for debugging?▼

You should not use automated resolution docs for debugging when a problem lacks a confirmed fix, verified resolution steps, or clear root cause analysis, as the schema validation requires complete context to generate a valid file.

Related Skills

Explore More Software Engineering Skills→
merlyn-huntressmerlyn-huntress

compound-docs

Captures solved technical problems into categorized markdown documents with validated YAML frontmatter.

Community
Advanced
BradliebsBradliebs

ce-compound

Coordinate subagents to document solved problems into a searchable knowledge base.

Community
Advanced
EveryIncEveryInc
24.1k

compound-docs

Generate categorized markdown documentation with YAML frontmatter for solved problems.

Official
Advanced
hoanghd218hoanghd218

debug

Trace bugs to root causes using systematic debugging phases and validation.

Community
Advanced