wild-risa-balancelisted

# WILD / RISA Balance ## When to Use - Emitting a multi-item recommendation block (≥3 items) - Choosing between a safe option and a bold option - Reviewing your own plan for over-cautiousness or over-fantasy - Pairing with `proceed-with-the-recommendation` to decide which items belong above and below the cut ## The Two Modes ### RISA (Execution) - **R**ealistic — fits the constraints in front of you - **I**mportant — moves a stated goal, not a vanity metric - **S**pecific — names files, commands, or owners - **A**greeable — the operator can approve it without a meeting If you only stay in RISA, you ship safe, average results. ### WILD (Creation) - **W**ild — breaks the default frame - **I**maginative — invents an option that did not exist a minute ago - **L**imitless — ignores current budget, headcount, or stack - **D**isruptive — replaces a workflow rather than tuning it If you only stay in WILD, you generate cool ideas that never ship. ## The Trap RISA alone produces a backlog of incremental fixes that never compound. WILD alone produces a graveyard of demos that never reach production. The bigger failure is unconscious switching: drifting into WILD during execution, or drifting into RISA during brainstorming, without naming the switch. Name the mode you are in before you write the next line. ## Switching Deliberately | Phase | Mode | Why | |-------------------------|-------|---------------------