workflows-compound

Coordinate solved problem documentation into a searchable docs/solutions entry with YAML frontmatter.

Updated Aug 27, 2026

Search Tags:#documentation #knowledge #workflows #document #solutions #team

Ready to run

npx skills add https://github.com/mattjefferson/open-compound-engineering --skill workflows-compound

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflows-compound
Source: https://github.com/mattjefferson/open-compound-engineering/tree/main/skills/workflows-compound
Command: npx skills add https://github.com/mattjefferson/open-compound-engineering --skill workflows-compound

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document the results of a solved problem to create structured, searchable knowledge that accelerates future work.

Core Features & Use Cases

Coordinates parallel subagents to capture context, root cause, solution, and prevention guidance
Produces a single, well-structured documentation file placed under docs/solutions with a searchable YAML frontmatter
Enables rapid reuse: next time a similar issue arises, teams can reference the compiled solution

Quick Start

Document the most recent solved problem to generate a single, searchable documentation entry.

Frequently Asked Questions about workflows-compound

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

FAQPage Schema

How do I document solved problems so my team can reference them later?▼

Documenting solved problems requires capturing context, root cause, solution, and prevention guidance into a centralized knowledge base. This Skill coordinates parallel subagents to compile that information into a single searchable docs/solutions entry with validated YAML frontmatter for rapid future reuse.

What is the best way to create structured team knowledge from incident resolutions?▼

Creating structured team knowledge from incidents involves orchestrating documentation of root causes and preventive guidance. This Skill generates a well-structured file under docs/solutions with searchable YAML frontmatter, accelerating future work by enabling rapid reference when similar issues arise.

How does writing a docs/solutions entry with YAML frontmatter work?▼

Writing a docs/solutions entry with YAML frontmatter works by orchestrating parallel subagents to extract problem context, root cause, solution, and prevention guidance, then validating the YAML frontmatter to produce a single, searchable documentation file for future team reference.

Do I need a specific docs/solutions directory setup to document problem resolutions?▼

Documenting problem resolutions requires a docs/solutions directory where the compiled entry will be placed. No external dependencies are needed, but the orchestration validates the YAML frontmatter to ensure the resulting knowledge base file remains structured and searchable.

Can I capture context and root cause for every solved problem my team finishes?▼

Capturing context and root cause for solved problems is fully supported. Applicable whenever teams finish a problem, the Skill coordinates subagents to extract context, root cause, solution, and preventive guidance, validating everything into a single centralized knowledge base entry.

What are the limitations of using YAML frontmatter for knowledge base documentation?▼

Using YAML frontmatter for knowledge base documentation requires validation to maintain searchability. The Skill orchestrates this validation to ensure the docs/solutions entry is correctly structured, but it focuses on compiling solved problems rather than managing the broader documentation site infrastructure.