add-delivery-modelisted

# Delivery Mode <!-- uses: - mention: /add.brainstorm - mention: /add.new - mention: /add.plan - mention: /add.build - mention: /add.review - mention: /add.done - mention: add-doc-schemas - mention: add-review-discipline --> > **LANG:** Respond in user's native language (detect from input). Tech terms always in English. Short sentences, one idea each; the common word over the rare one; a technical term explained in one line the first time it appears. Owns HOW a delivery moves through the pipeline once the user has approved it: the two modes, where each is carried, which stops wait, how one command hands off to the next, and where the automatic path ends. WHAT each command presents at a stop belongs to that command — every command classifies its own stops where they sit. ## When to Use - A command is about to stop and has to know whether the stop waits. - A command has finished and is about to suggest, or run, the next one. ## When NOT to Use - Writing the intent file's shape — the `brainstorm-intent` schema in `add-doc-schemas` owns it. - `/add.done`. The close-out is never part of an automatic delivery, so nothing here reaches it. --- ## The Two Modes **Chosen once, at `/add.brainstorm`'s approval, and carried — never asked again.** | Mode | What the user chose | |---|---| | `confirm` | See every stage. Each stage stops, shows its work and waits | | `automatic` | Deliver without waiting. Each stage hands off to the next until a stop that needs a person | ### Wher