archflow-modelisted

> Arguments are the text after the skill name. # /archflow-mode — Show or switch the ceremony mode (quick | full) Argument (`the text the user wrote after the skill name`): optional target mode `quick` or `full`. Empty → show the current mode. `mode` is a profile over the SAME v2.0 schema, not a fork. It governs how much ceremony is enforced. Switching is an in-place change — no data rewrite, because the schema is identical in both modes. ## Usage ``` /archflow-mode → show the current mode + what it means /archflow-mode full → switch to full /archflow-mode quick → switch to quick ``` ## The two modes | Concern | `quick` (small / solo) | `full` (team / scale) | |---|---|---| | Releases | one implicit release; no create/ship ceremony until asked | explicit release pipeline + ship ritual | | Backlog | stories may live directly in the release | backlog stubs → promote → detailed | | Readiness gates | **auto-satisfied** (exist but don't block) | enforced **advisory-recorded** (`started_ungated` on override) | | Approval gates | proceed unless the user stops you | explicit per-phase approval | | Roles | one lane (solo) | PM / designer / architect / engineer / QA lanes | ## Show current mode (no argument) Read `mode` from `.archflow/roadmap.yaml` (source of truth; mirrored in `current-phase.yaml`). Print it and a one-line description. If absent, treat as `quick` and offer to record it. ## Switch mode 1. Set `mode` in `.archflow/roadmap.yaml` AND `.archflow/c