Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/ce-compound/SKILL.mdThis skill does one of two jobs. Capture holds the lesson of one solved problem. Refresh audits the existing learnings against the current codebase and can delete docs and open a PR.
Run refresh when the arguments contain mode:refresh, or when an interactive run was invoked to do one, as in /ce-compound refresh payments, "clean up the learnings", or a standalone request to create CONCEPTS.md. An earlier remark in the session does not count. Read references/refresh/overview.md and follow it instead of the rest of this file. The refresh references name the parts of this file they reuse.
When an interactive run is asked to create or update the project's coding standards or review docs as a whole, invoke the ce-setup skill with standards and stop.
Otherwise run capture. A non-interactive run without mode:refresh is always capture, whatever its context says. Capture takes free-text context, so refresh token rotation after fixing that bug is a capture. If an interactive run's words could mean either job, ask once with the host's blocking question tool, and capture if there is no answer.
Outcome: the lesson of one qualifying solved problem is held in the cheapest form that stops the repeat, grounded against the current tree, discoverable by the next agent.
Done: the chosen form is written or updated and validated, vocabulary capture recorded, and the mode's completion report emitted; when no lesson qualifies, nothing is written and the report says why.
One learning per run. A session that produced several gets several sequential runs, never one batched run. Read references/research.md; it explains what batching breaks.
Document only a problem that is solved and verified.
A lesson earns a durable form only when it holds durable project reasoning that is not readily recoverable from the current code, tests, checks, coding standards, comments, or documentation, and losing it would plausibly cause recurrence, material risk, or substantial rediscovery. Apply this counterfactual: without a record of this lesson, would a future engineer working from the current tree still be likely to repeat the mistake or redo substantial investigation? Completion, effort, and diff size do not establish eligibility.
If the counterfactual fails, write nothing and report why. Judge this from the session rather than asking. An explicit invocation requests the judgment now but does not lower the bar.
An existing learning that became materially inaccurate or incomplete qualifies because leaving it would mislead. Update that learning instead of creating a duplicate.
Enter non-interactive mode when either holds: the arguments you were invoked with contain the mode:non-interactive token or its deprecated alias mode:headless, or the invocation makes non-interactive intent unmistakable, such as a caller or standing instruction asking to run ce-compound "headless", "non-interactively", "unattended", or "without prompts/questions". Both tokens together is not a conflict. Bare "automatically" or "auto-run" is not on its own a non-interactive signal: it speaks to invoking the skill, not to suppressing its prompts. An ambiguous or absent signal defaults to interactive. Tokens starting with mode: or depth: are flags, not context: strip them before treating the remainder as the brief context hint. Once detected, non-interactive mode applies for the entire run.
references/modes.md decides depth, including what a depth: token does, as in mode:non-interactive depth:lightweight or mode:non-interactive depth:full. Read it before step 1.
Non-interactive mode asks nothing. It asks no blocking question of any kind, in any phase, because a caller reaching this path has no human to answer one. Every non-interactive exit, including one taken before any phase runs, ends on a terminal signal a caller parses: Documentation complete, or Documentation skipped with the reason when the run wrote nothing. Interactive mode asks only where a step's own reference says to.
Resolve <root> when you first compose a <root>/solutions/ path, and pass a subagent the resolved path rather than the config.
Resolve the CE artifact root <root> before composing any artifact path.
docs_root from <repo-root>/.compound-engineering/config.yaml only (<repo-root> = git rev-parse --show-toplevel). Do not read it from config.local.yaml. Unset -> <root> is docs, exactly as before..git/. Otherwise stop with an error naming docs_root and the value -- never fall back to docs.<root> as the sole artifact location: create it if absent, compose each path as <root>/<subdir> with this skill's own subdirectory, and never also read docs.Only the orchestrator writes product files. Phase 1 subagents write to per-run scratch only, and never touch <root>/, project instruction files, or any other tracked path.
The orchestrator writes what references/form.md chooses, in every mode and without asking: at most one added test, added or tightened lint rule with any baseline entries it needs, or condition in an existing CODING_STANDARDS.md, and at most one learning under <root>/solutions/. It never changes product code. It also writes two maintenance side effects that their own step describes: CONCEPTS.md during vocabulary capture, and — only in interactive Full mode after consent — a small discoverability line in a project instruction file. Two further writes exist only in interactive Full mode when the user selects them at the assembly destination step: a rule file inside a writable declared Compound Pack, and the packs: entry appended to .compound-engineering/config.yaml. An instruction file is only ever edited, never created. Nothing else in the tree is written. Edits to other docs belong to a refresh, which a capture recommends or runs with a narrow scope.
Run these in order. Each reference is a required read at the step that names it.
references/research.md.references/session-history.md, and start it after dispatching the Related Docs Finder so it overlaps your drafting rather than serializing.references/form.md and write what it chooses, then read references/assembly.md.references/refresh-and-discoverability.md.references/enhancement.md. Interactive only.references/report.md for the report shape your mode must emit and how the skill ends.Lightweight Mode replaces steps 1-6 with a single pass; read references/lightweight.md, which defines its own completion output for both modes.
EveryInc/compound-engineering-plugin
ee46dde
Also appears in
last in sync Sep 16, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.