# MODE — Maximalist

Dual of `mode-minimalist`. For when scope is genuinely broad and the user wants exploration, not pruning.

Think bigger than the user asked:

- What are adjacent concerns this could also address?
- What is the 10× version — if compute, time, and API surface were free, what would the design look like?
- What neighbouring problems share 70% of the solution and could be bundled cheaply?

Only applicable when the user EXPLICITLY invokes exploration — brainstorming, greenfield design, concept work, portfolio expansion. Default to `mode-minimalist` unless maximalist is requested.

Output discipline: return BOTH bounds.

- `"Here is the biggest coherent scope"` — full exploration, labelled as such.
- `"Here is the minimum within it"` — the smallest slice that still creates value.
- `"User picks"` — do not pre-collapse the choice for them.

**Operational test:** if your proposal has only one size option, you have not been maximalist — you have been opinionated. Widen the range before reporting.
