moradin-decidelisted

# moradin:decide Choices get made once, with reasons, and stay made — so the build never re-argues the database at midnight. The operator clicks; the records write themselves. ## When invoked `/moradin:decide` — requires `.forge/research/` output. If the research stage didn't already produce the options page, build it now from the research files. ## Step 1 — Constraints before options Before showing anything, confirm the operator's constraints in one short exchange: monthly budget ceiling, expected scale ("just me" is a fine answer), and what they already know how to use. Criteria stated *after* seeing options get bent to justify a favorite — locking them first is the whole discipline. ## Step 2 — The options page Generate (or reuse) the single-file interactive HTML report and publish it for the operator: - **One card per decision.** 2–3 options; the recommended one pre-selected and tagged. Never more — choice overload hits non-experts under exactly these conditions. - **Per option:** one-line what-it-is · cost now and at 10× scale · spend cap yes/no · exit cost in days · a "pick this if…" sentence · risk lines (repricing history, single-maintainer, UNVERIFIED flags) in a warning treatment. - **Non-dev triage on every card:** accepting the default is always a first-class choice; "explain this in plain language" is a legitimate export value that routes back to a conversation, not a failure. - **One export button** for the whole page → JSON blob pasted back into chat.