lfg

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

When invoking any skill referenced below, resolve its name against the available-skills list the host platform provides and use that exact entry. Some platforms list skills under a plugin namespace (e.g., galeharness-cli:gh-plan); others list the bare name. Invoking a short-form guess that isn't in the list will fail — always match a listed entry verbatim before calling the Skill/Task tool.

1. Invoke the gh-plan skill with $ARGUMENTS.

   GATE: STOP. If gh:plan reported the task is non-software and cannot be processed in pipeline mode, stop the pipeline and inform the user that LFG requires software tasks. Otherwise, verify that the gh:plan workflow produced a plan file in docs/plans/. If no plan file was created, invoke gh-plan again with $ARGUMENTS. Do NOT proceed to step 2 until a written plan exists. Record the plan file path — it will be passed to gh:review in step 3.

2. Invoke the gh-work skill.

   GATE: STOP. Verify that implementation work was performed - files were created or modified beyond the plan. Do NOT proceed to step 3 if no code changes were made.

3. Invoke the gh-review skill with mode:autofix plan:<plan-path-from-step-1>.

   Pass the plan file path from step 1 so gh:review can verify requirements completeness.

4. Invoke the test-browser skill with mode:pipeline.

5. Invoke the git-commit-push-pr skill.

   This commits any remaining changes, pushes the branch, and opens a pull request. If a PR already exists (check with gh pr view --json number,url,state 2>/dev/null), skip PR creation but still commit and push any uncommitted changes.

6. Output <promise>DONE</promise> when complete

Start with step 1 now. Remember: plan FIRST, then work. Never skip the plan.