ce:compound

ce:compound is the capture skill inside the compound-engineering plugin: the command you run to turn a problem you just solved into a durable learning file. Its unit of output is one markdown document under `docs/solutions/<category>/`, whose frontmatter (`title`, `tags`, `module`, `problem_type`, `applies_when`, `severity`, `date`) exists to serve retrieval rather than presentation.

Two design decisions are worth noting, and the sources record both. Trevin Chow's Compound Engineering v2.60.0, dated 31 March 2026, gave ce:compound a per-track schema separating bug (what broke) from knowledge (what was decided or discovered), plus a discoverability check. The Thinkroom agent guide of 2 July 2026 explains the reasoning behind that split: a system that only remembers bugs forgets the essential part.

The second decision is about timing. ce:compound documents while the context is still fresh, on the premise that the binding constraint is not writing but retrieval, and that postmortems written later rot in wikis. Execution fans out to subagents (a context analyzer, a solution extractor, a duplicate finder) while the orchestrator alone writes a single document.

Kieran Klaassen's Thinkroom guide places ce:compound at the start of a loop it calls the Compounding Knowledge Lifecycle, with capture as principal and automatic retrieval as interest. The canonical example given there is incident #714 becoming a fix, a learning, a test and a doctrine at once, which reframes compounding as removing classes of failure rather than accumulating documents.