Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.
88%
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
Bundled references must be read, never approximated. Resolve each reference or script path named below from this skill's loaded SKILL.md directory, using the full skill path the harness supplied, and never glob the target repository to find a bundled file. Read each reference when you enter the phase it governs; a read made before that phase does not satisfy it. A reference this file says to read again is read again at its step only when its full text is no longer in context, as after a compaction. If the harness does not expose the skill directory, or a required file cannot be read, stop before the action it governs and report which file is missing. Do not reconstruct its rules from memory; report the missing reference instead of continuing natively.
Recovery activation comes first. Before classifying the input as a plan, a path, a blank, or a bare prompt, recognize requests to resume, inspect, reap, or clean up an existing run. Recovery never dispatches a new worker, selects a new route, discovers another plan, reruns completed verification, or enters either shipping path. If the run id is missing, ask for it; never guess one.
Before any other input decision, read references/input-triage.md. It decides the source, control tokens, recovery, read-only discovery, plan readiness, and bare-prompt sizing. Three rules from it hold here:
ce-plan already sized in this session is executed, not planned again. A decision the user would weigh is asked as a question, never as a route back to ce-plan or ce-brainstorm.When triage selects Return-to-Caller Mode, read references/return-to-caller.md immediately and record that it governs how this run ends. If it cannot be read, stop before any mutation; do not fall back to standalone behavior.
Establish the workspace. Before moving branches, editing, dispatching, or committing, read references/workspace-setup.md. It decides the checkout, branch, dirty files, and task setup. Never write without a writable canonical checkout, and never write on the real default branch unless the user explicitly directed that in this session.
Do not commit or publish anything the user did not offer. When a unit needs a file that was already dirty, standalone mode asks once whether to include or exclude that file. Return-to-Caller Mode neither asks nor edits it; it returns blocked, naming the collision and how to recover.
Resolve the engine, then strategy. After bounded plan intake and task derivation, but before selecting a unit for execution, writing, dispatching, or committing, read references/execution-engines.md and complete its route selection. It applies with or without a typed binding; native execution is eligible only when that reference selects it or exhausts an allowed fallback. The engine choice never changes which reference governs how the run ends.
If cross-model execution is selected, read references/cross-model-execution.md before any content or authority crosses to the other model. It defines controller initialization, the post-init engine lock, bounded egress, transactions, recovery, and receipts.
On native execution, work that is one unit, or units that each depend on the one before, runs inline in this context without that reference. Otherwise, before choosing inline, serial, or parallel execution, and before dispatching any worker, read references/execution-strategy.md. It decides scheduling, worker packets, and integration. The host orchestrator keeps authoritative verification and makes the canonical commits.
Before the first implementation write, including on the Trivial route, read references/implementation-loop.md. It decides evidence, verification, per-unit commits, and simplification.
The commit rule from this file stays in force throughout: every implementation commit names only that unit's owned files. A bare git commit can absorb the user's pre-existing index, so it is forbidden.
Keep going until every in-scope unit is done. A progress update does not end the run; stop before that only for a named blocker.
After the tasks and local verification are complete, standalone mode reads references/shipping-workflow.md before any quality check or delivery. It decides simplification, code review, final validation, and delivery.
Code-review completion gate (standalone only). Code review must actually happen before shipping. The run is not done, must not call a commit or shipping skill, and must not report that shipping is complete until the shipping reference has recorded either an actual completed ce-code-review receipt or one of its exact authorized skip states. Never substitute a mental self-review or findings already applied earlier. This rule does not apply in Return-to-Caller Mode.
Return-to-Caller Mode performs implementation and local verification only. It must not enter Phase 3-4 or run final simplification, code review, PR creation, CI watching, babysitting, or any other standalone shipping action; the caller owns those steps.
Immediately before emitting the result, read references/return-to-caller.md again. It alone defines the full return result, the check that evidence is complete, the route and model records, recovery semantics, and standalone_shipping_skipped: true. Do not build a complete result from this file.
If that required read fails after planning or implementation created state, preserve every changed file, commit, workspace, and controller record. Return the minimum blocked result from this file: status: blocked, plan_path, run_id when known, changed_state, blockers naming the missing reference, and recovery_path. Do not erase partial state, report success, or fall into the standalone shipping path.
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.