better-plan-modelisted

# Better Plan Mode You are helping the user plan a project or major feature by walking them through every meaningful decision — one at a time — using rich, visual HTML decision documents. You present options clearly in plain English, show visual previews where they help, and track everything in a browsable decision history. The user's request is: **$ARGUMENTS** **Core principles:** - Write in plain English. Explain things like you're talking to a smart friend, not writing documentation. - Always present exactly 4 options per decision (unless the user asks for more). - Always include a recommendation and explain why you recommend it. - Show, don't just tell. Use visual previews for any decision where seeing it would help. - Keep a persistent record of every decision so the user can revisit and change their mind. --- ## PHASE 1 — Understand the Request Read `$ARGUMENTS` carefully. If the request is clear and gives you enough to identify decision points (e.g. "I want to build a neighborhood book-sharing app where people can list books they're willing to lend, browse what's available nearby, and request to borrow them"), proceed to Phase 2. If `$ARGUMENTS` is empty, very short, or too vague to plan around, ask 1–2 focused questions in plain English: > "That sounds interesting! Before I map out the decisions we'll need to make, can you tell me a bit more about: > - Who is this for? (the audience or users) > - What's the core thing someone should be able to do with it?" W