ce-compound

Coordinate parallel subagents to write structured Markdown solution documents.

Updated Mar 12, 2026

Search Tags:#workflow #documentation #markdown #subagents #knowledge #postmortem #compounding

Ready to run

npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-compound-datorresb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-compound
Source: https://github.com/datorresb/discovery-event-platform/tree/main/.github/skills/ce-compound
Command: npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-compound-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and documents recently solved problems to compound team knowledge, turning hard-won insights into reusable references.

Core Features & Use Cases

Coordinates multiple subagents to document solutions in parallel, producing structured, searchable Markdown files.
Writes a single final document under docs/solutions with YAML frontmatter for discoverability and cross-reference.
Use cases include post-mortems, onboarding new engineers, and preserving knowledge for faster future resolutions.

Quick Start

To start documenting a recent fix, run /ce-compound with optional context to generate a structured knowledge document.

Frequently Asked Questions about ce-compound

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

FAQPage Schema

How do I document solved problems into searchable Markdown for team knowledge?▼

Document solved problems by orchestrating parallel subagents to extract context, categorize solutions, and write a final Markdown file with YAML frontmatter under docs/solutions for cross-reference and discovery.

What is the best way to structure post-mortem documentation for engineering onboarding?▼

The best way to structure post-mortem documentation is generating a single Markdown file with YAML frontmatter, organizing content by category under docs/solutions to preserve knowledge for faster future resolutions.

How does a multi-phase workflow capture prevention strategies in knowledge documentation?▼

A multi-phase workflow captures prevention strategies by running parallel subagents through context analysis, solution extraction, related docs identification, and category classification before writing the final document.

Do I need any dependencies to generate structured solution files with YAML frontmatter?▼

No dependencies are required to generate structured solution files with YAML frontmatter; the skill coordinates subagents internally to produce the final Markdown output under docs/solutions.

Can I run specialized reviews during post-mortem documentation generation?▼

Yes, you can run optional enhancement steps for specialized reviews during the documentation workflow, adding targeted analysis layers after the core solution extraction and category classification phases complete.

When should I avoid using subagents to compound team knowledge?▼

You should avoid using subagents for knowledge compounding when your solved problem lacks sufficient context for extraction, as the multi-phase workflow requires analyzable context to produce a meaningful, searchable Markdown document.