lfg
Run the full autonomous shipping pipeline end-to-end, hands-off with no check-ins. Use only when the user explicitly asks to build or ship something autonomously all the way to an open PR, or invokes lfg directly — it pushes and opens a PR without stopping. Not for in-the-loop work where the user reviews each step: use ce-plan, ce-work, ce-debug, or ce-commit-push-pr instead.
Install
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/lfg ~/.claude/skills/lfgFrom README
Per-stage routing carriers Before step 1, judge whether the conversation expresses semantic intent to assign a stage — planning or implementation — to a model or harness; a plain mention in feature content, quotes, comparisons, or a filename is not an assignment. When one exists, read references/stage-routing.md before step 1: only it carries the routable stages, scope and strength resolution, the implementationengine grammar, ordered fallback, the sanitization that keeps routing out of planning and review inputs, and both seams' carrier strings. An improvised carrier drops the user's instruction or contaminates the plan with routing. Read references/plan-brief.md first, then invoke the ce-plan skill with the sanitized feature request — or the arguments you were invoked with, unchanged, when no routing directive was present — prefixed with the planmodel: carrier when a planning-stage directive resolved, and with the settled-decisions brief that file specifies.