lfg

CRITICAL: You MUST execute every step below IN ORDER. Do NOT jump ahead to coding or implementation. The plan phase (step 1) MUST be completed and verified BEFORE any work begins.

LFG runs hands-off, from schedulers, loops, and nested orchestrators with no user to answer, so no step stops to ask. The one exception is the upfront routing question references/stage-routing.md defines.

Resolve every skill named below against the host's available-skills list and invoke that exact entry; some hosts namespace it (compound-engineering:ce-plan), and a short-form guess that is not in the list fails.

Read references/task-visibility.md before step 1: it owns the stage-level view this pipeline publishes through the platform's task-tracking capability, the per-step chat narration, and the completion discipline — a step is done only after it ran, and the turn does not end before DONE or a GATE stop.

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 implementation_engine 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.

1. 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 plan_model:<alias> carrier when a planning-stage directive resolved, and with the settled-decisions brief that file specifies. Only it carries the artifact-root rule this step's gate reads, the brief's required fields, demotion rule, topical scope bar, and skip-entirely case, and the readiness values the gate applies.

   GATE: STOP. Stop the pipeline and tell the user why when ce-plan reports the task is non-software (LFG requires software tasks), returns any explicit status: blocked report (including settled-decision-invalidated), or when the plan it wrote fails the readiness check in references/plan-brief.md. Blocked status outranks an existing artifact and is never retried. Only absence of both a blocker and a plan file ce-plan reported writing this run invokes ce-plan again with those same arguments, reusing the composed brief verbatim; never proceed to step 2 without a written plan.

   Record the plan file path — it is passed to ce-work in step 2 and ce-code-review in step 4. LFG never launches /goal directly; ce-work owns any goal-mode or dynamic-workflow engine choice and returns control to LFG afterward.

2. Read references/work-return.md first, then invoke the ce-work skill with mode:return-to-caller <plan-path-from-step-1>, or with the carrier form from references/stage-routing.md when a routing carrier resolved. Only it carries what each return status means, the receipt fields a status: complete return must contain, the verification-evidence contract, how settled_decision_conflicts route, and the one recovery invocation. Accepting a return without it ships work that nothing protected.