Idea to Plan

Convert an underspecified request into (1) a one-paragraph problem statement, (2) a scoped spec, and (3) a phased implementation plan — each shown to the user for sign-off before moving on. Never jump to code from a vague prompt.

When to use

• The request is a goal, not a specification ("build a dashboard", "add auth").
• Requirements, constraints, or success criteria are missing or implied.
• The user is exploring whether something is worth building.

Do not use this for well-specified tasks, bug fixes with a clear repro, or mechanical changes — those go straight to implementation.

Procedure

1. Restate the problem (before asking anything)

Write one paragraph: who has what problem, why now, and what "solved" looks like. Show it. If you can't write it, you don't understand the request — that gap is your first question.

2. Ask only decision-changing questions