mkadvise

# Advise One question at a time until the problem is confirmed, then one honest verdict. ## What This Is (and what it is not) Advise sits between interrogation and implementation. It **interviews** like `mk:grill`, but grill deliberately stops before recommending anything — advise exists to recommend. It **weighs options** like `mk:brainstorming`, but brainstorming enumerates alternatives for a problem you have already validated — advise starts before that, by questioning whether the problem is even the right one, and ends with a single pick rather than a menu. The whole value is the reframing. A user asking "should I use Redis or Memcached" often has a problem that needs neither. Answering the question as asked is the failure mode; the job is to find the real question first, confirm it with them, and only then answer. ## Route Fences | If the user wants��� | Use | Not advise, because… | |---|---|---| | To be interrogated on their own plan, no answers given | `mk:grill` | Grill never recommends; advise exists to recommend | | Alternatives compared for a validated problem | `mk:brainstorming` | Advise questions the problem itself, and picks one option | | "Is this worth building at all?" | `mk:office-hours` | That is a product-existence question, upstream of advice | | Several perspectives to argue a trade-off | `mk:party` | Advise is one advisor giving one verdict | | A plan with phases | `mk:plan-creator` | Advice is not a plan; see Boundaries below | Overlap is the f...