ce:compound

Coordinate subagents to document solved engineering problems in docs/solutions/.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-compound-michaelvolz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:compound
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-compound
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-compound-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

ce:compound turns a solved engineering issue into a durable knowledge asset by orchestrating parallel subagents to capture symptoms, resolutions, and prevention guidance before the context fades. It enforces schema-backed frontmatter, category mapping, and discoverability so future teammates can find the story in docs/solutions/ without digging through chat history.

Core Features & Use Cases

  • Parallel research orchestration: Launches context analysis, solution extraction, and related-doc discovery agents in sync, keeping their outputs text-only until the orchestrator assembles the final documentation.
  • Schema & template driven: Loads references/schema.yaml, yaml-schema.md, and the resolution template to validate frontmatter (module, component, severity, problem_type) and keep every doc consistent.
  • Discoverability hygiene: Uses the discoverability check to ensure AGENTS.md or CLAUDE.md surface the knowledge store, and stores finalized solutions under docs/solutions/[category]/ with YAML metadata for searchability.

Quick Start

Call /ce:compound with a short summary of the verified fix you want to capture.

Frequently Asked Questions about ce:compound

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

FAQPage Schema
How do I document bug fixes and engineering resolutions for future reference?

Parallel subagents analyze context, extract the solution, and discover related documentation simultaneously, keeping outputs text-only until an orchestrator assembles the final, consistent resolution document with schema-validated frontmatter.

How do I ensure my engineering knowledge base has consistent metadata and schema validation?

Schema validation ensures consistent metadata by loading YAML schemas and templates to validate frontmatter fields like module, component, severity, and problem_type, keeping every captured solution document structured and uniform.

What is the best way to capture solved engineering problems before context fades?

The best way to capture solved problems is orchestrating parallel subagents to immediately extract symptoms, resolutions, and prevention guidance, turning verified fixes into durable, searchable knowledge assets under docs/solutions/[category]/.

How do I make archived engineering solutions discoverable for my team?

Discoverability is achieved by storing finalized solutions with YAML metadata under docs/solutions/[category]/ and running checks to ensure project files like AGENTS.md or CLAUDE.md surface the knowledge store for team searchability.

Do I need a verified fix before documenting a solution with structured knowledge capture?

Yes, you need a recently verified fix or workflow improvement. The process targets engineering workflows that require structured knowledge capture for bug fixes, taking a short summary of the verified fix to generate the documentation.