compound-docs

Generate standardized Markdown solution docs with pattern detection.

5|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/Bind/skillz.sh --skill compound-docs-bind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/Bind/skillz.sh/tree/main/.opencode/skill/compound-docs
Command: npx skills add https://github.com/Bind/skillz.sh --skill compound-docs-bind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture solved problems as searchable documentation with pattern detection.

Core Features & Use Cases

  • Auto-trigger: the skill activates when a fix is confirmed or the /compound command is issued.
  • Schema-driven documentation: validates frontmatter against schema.yaml and allows evolving enums as teams encounter new values.
  • Consistent solution docs: generates standardized Markdown docs with symptoms, category, root cause, solution, and prevention.
  • Knowledge reuse: builds a central repository of documented solutions for future reference and pattern discovery.
  • Extensible workflow: supports adding new categories, components, and root causes on demand.

Quick Start

Use the compound-docs skill to capture a solved problem into documentation after a fix, or run the CLI to add compound-docs and start a documentation workflow.

Frequently Asked Questions about compound-docs

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

FAQPage Schema
How do I capture solved debugging problems into searchable Markdown documentation?▼

Capture solved debugging problems by triggering automated post-mortem workflows that validate frontmatter against schema.yaml and generate standardized Markdown solution docs with symptoms, root cause, and prevention fields.

What is pattern detection for knowledge management in software development?▼

Pattern detection for knowledge management is the automated recognition of recurring issues across a repository of standardized Markdown solution docs, enabling teams to discover repeated symptoms and root causes during post-mortems.

How do I validate Markdown frontmatter against a schema for technical documentation?▼

Validate Markdown frontmatter against a schema by enforcing schema.yaml rules during the documentation generation process, ensuring required fields like date, category, and symptoms are correctly formatted before saving the solution doc.

Can I add new categories and root causes on demand to a documentation schema?▼

You can add new categories and root causes on demand to a documentation schema by evolving the frontmatter enums in schema.yaml as teams encounter new values during their debugging sessions and post-mortems.

What is the best way to document post-mortems for development teams?▼

The best way to document post-mortems for development teams is using a schema-driven Markdown approach that auto-triggers when a fix is confirmed, ensuring consistent capture of symptoms, solutions, and prevention strategies for future pattern discovery.

Does this knowledge capture workflow support manual triggering alongside automated fixes?▼

The knowledge capture workflow supports manual triggering alongside automated fixes by activating when a fix is confirmed or when the /compound command is issued, allowing flexible documentation generation during post-mortems.