One-Shot

Plan and implement a small task in a single session. This is the lightweight sibling of the create-plan → implement-plan pipeline: same discipline (written plan, verification, code review), a fraction of the ceremony.

Scope gate (HARD rule)

One-shot is for small work only: at most ~3 phases, one subsystem. Check this at every stage — assessment, planning, and mid-implementation. The moment the work reveals more phases or a second subsystem, STOP:

1. Tell the user what grew and why.
2. Hand off to /desplega:create-plan, passing the yolo plan (whatever exists of it) as input context.

Grinding on past the gate is how one-shots turn into unreviewable mega-diffs. Escalating is success, not failure.

Step 1: Assess ceremony

Read the prompt and decide dynamically:

• Clear enough (goal unambiguous, approach obvious, no real trade-offs) → GO. No questions.
• Not clear → one lowkey grill: a single bundled AskUserQuestion call with 2–3 decisions max, every question shipping a recommended answer (per desplega:ask-user conventions). Facts-vs-decisions rule applies (as in desplega:brainstorming): look up facts yourself — via quick background sub-agents routed per desplega:delegate-work — and only bring genuine decisions to the user. One round only; if the answers reveal a swamp, that's the scope gate firing.