go

# Landing Mode Take the already-converged research conclusion and land it as MVP slices continuously and automatically; each stage closes its own verification loop, with one end-to-end recap at the very end. ## Trigger conditions (all must hold) 1. The research / discussion phase has ended and the conclusion has converged 2. The user explicitly says "start landing / implement / go" 3. The user wants continuous, automatic progress without per-stage confirmation If any condition fails, fall back to `qa` mode for clarification first. ## Pre-flight check (mandatory before starting) Confirm the following are **in hand**; if any is missing, stop and ask — do not guess: | Item | Source | |---|---| | Research conclusion | Session context / a path the user gives / pasted text | | Landing scope | What's in, what's out | | Acceptance criteria | What counts as "end-to-end runs" | | Working directory and stack | Project root path, language, framework | ## Execution loop ``` while there are unfinished MVP sub-tasks: 1. Pick the next minimum closed-loop sub-task - Deliverable: a standalone artifact - Verifiable: a clear way to run / check it 2. Write code (minimum change, KISS) 3. Self-verify: run commands, hit endpoints, read output — do not wait for the user's nod 4. Emit [Stage N delivery summary + verification report] 5. No pause; proceed to the next stage end while Finally emit [Overall recap: end-to-end interaction verification + total delivery list] ``` ...