
Keeps your docs/solutions/ directory honest by comparing learnings and patterns against the current codebase. When you run "refresh my learnings" or "audit docs/solutions/", it classifies each doc as Keep, Update, Consolidate, Replace, or Delete based on code drift. The workflow processes learning docs first since they're primary evidence, then updates any pattern docs that depend on them. Ships with a headless mode for CI or bulk cleanup that skips all questions and generates an applied/recommended report. The interaction model is borrowed from ce-brainstorm: one blocking question at a time, multiple choice when possible, lead with a recommendation. It's maintenance tooling that assumes git history is your safety net.
$ npx -y skills add everyinc/compound-engineering-plugin --skill ce-compound-refresh --agent claude-codeInstalls into .claude/skills of the current project.
This name still works, so existing prompts and schedules keep running. The refresh itself now lives in ce-compound.
Done: the notice was shown before and after the refresh, and the refresh ran with the scope and mode it was asked for.
Render the invocations in the notice for the active host: /skill-name by default, and $skill-name on Codex or another host that documents dollar-prefixed invocation. Output one form only.
Do these in order:
Print this notice, unchanged apart from the rendering:
⚠️
/ce-compound-refreshhas merged into/ce-compoundand will go away in an upcoming release. This run continues as normal. Next time, use/ce-compound refresh.
If your arguments contain mode:non-interactive or mode:headless, end the notice with this instead, because nobody is present and the plain word would run a capture: Next time, use /ce-compound mode:refresh mode:non-interactive.
Sponsors