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.