solutioninglisted

# Solutioning Facilitate choosing an approach when the problem is defined but the direction isn't. Explore options with the user, filter through simplicity, and record the decision for handoff to `creating-briefs`. Skip when only one viable option exists, the user has already committed to an approach, the choice is purely preferential, or the problem itself is still unclear (`understanding-the-ask` first). ## Workflow ### Step 1 — Classify the decision Ask: "How expensive would this be to reverse? If we try it and it doesn't work, can we go back?" - **Reversible (two-way door)** — file structure, naming, process experiments. Decide quickly at 70% confidence and course-correct as you learn. Watch for analysis paralysis. - **Irreversible (one-way door)** — core architecture, database selection, major dependency. Invest in understanding trade-offs before committing. Watch for premature commitment. The classification sets the evaluation depth for everything below. ### Step 2 — Establish the simplicity baseline "What's the simplest thing that could possibly work? Do we need this now, or are we anticipating future needs?" The simplest viable option becomes the baseline every other option must beat. - **YAGNI** — "we might need X later" → "do we need X now? If not, add it when we do." - **KISS** — "option A is more capable but complex" → "does simpler option B solve the current problem? Then complexity needs justification." - **Occam's Razor** — prefer the option making th