m_plan_rolllisted

# m_plan_roll One-shot, hands-off pipeline: **plan large → implement → deploy → verify**, no questions. A thin wrapper over `m_plan` (Phases 0–1) and `m_plan_implement` (execution) that swaps the interactive parts for autonomous defaults and maximum coverage. > This trades interactivity for autonomy. It still **cannot fake verification** and still **obeys the hard safety gates** below — those are the only things that can halt or block the run. ## Inputs - `$ARGUMENTS`: the task. If empty, ask once for the task, then stop asking. ## How it differs from `/m_plan` `m_plan` asks blockers and right-sizes. `m_plan_roll` does neither — it assumes the most thorough path and decides everything itself. ## Phase 1 — Plan (autonomous, large) Run `m_plan` Phases 0–1 with these overrides: - **No `AskUserQuestion`, no blocker batch.** For every blocker in `m_plan`'s `BLOCKERS.md`, pick the safest thorough default yourself. **Record each non-obvious decision** under a `## Assumptions` heading in `01_architecture.md` so the run stays auditable. - **Force size = large** → write **all 9** artifacts (`01`–`09`), maximum coverage (08 included). - **Gitignore:** append `.m_plan/` to `.gitignore` by default (no prompt); note it in the run log. - **No Approve pause.** Do not stop for `Approve? (yes / edit / stop)` — go straight to Phase 2. - Still obey `m_plan`'s artifact rules: a per-step check in every `05` step, build/test commands live only in `07`, fill every `<…>` placeholder, no secrets