gitnexus-lfg

Invoke /gitnexus-lfg with a task description or an existing plan file path. It runs gitnexus-plan, stops at a blocking gate for your approval, executes with gitnexus-work, and finishes with a gitnexus-review verdict and final report.

The gate presents the plan's summary and asks you to proceed to work or stop, keeping the plan file as the deliverable. Execution never starts without an explicit choice, and you can request a Deepen pass to strengthen the plan first.

Yes, pass a plan file path such as docs/plans/<plan>.md and the pipeline skips Lane 1, starting directly at the plan gate. All later lanes consume that recorded plan path.

In headless runs no one can answer the gate, so the pipeline ends after planning and delivers the plan file only. It never auto-proceeds to execution without a user decision.

For trivial or small-bounded tasks an agent finishes well under the ~35-turn planning boundary, planning costs more than it returns. The Skill detects this and offers gitnexus-work direct mode as an alternative before spending the plan lane.

No, the pipeline never pushes or opens a PR on its own. The final report lists commits, verification status, and review verdict, then offers pushing and PR creation as explicit next steps.