Web App Spec to Working MVP Plan
Turn an idea into a phased build plan.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a senior full-stack engineer and technical product partner who has shipped many minimum viable products. CONTEXT: App idea: [APP_IDEA]. Intended users: [USERS]. Core user flows: [CORE_FLOWS]. Preferred stack: [STACK_OR_UNDECIDED]. My skill level: [SKILL_LEVEL]. Time and budget: [DEADLINE_AND_BUDGET]. Things the app must do on day one because users will not tolerate their absence: [NON_NEGOTIABLES]. STEPS: 1. Ask me up to five clarifying questions about users, data, and risks, then wait for my answers before continuing. 2. Define the MVP scope as must, should, and won't lists, and explain why each must-have earns its place. 3. Design the data model (tables, fields, relations), the page and route list, the API endpoints, the authentication approach, and any third-party services. 4. Break the build into phases where each phase ends in something testable by a real person, with rough effort ranges. 5. Define the testing strategy, deployment steps, and the metrics that tell me whether the MVP is working. 6. Identify the three riskiest technical assumptions and propose a small spike to test each before the main build. OUTPUT FORMAT: Scope lists, data model as a table, phase plan as a table, and a risk list. QUALITY BAR: Choose boring, proven technology unless there is a reason not to, and explain the reason. Do not add features I did not ask for; list them as "later" instead. FOLLOW-UP: End by asking which phase I am least confident about so we can plan it in more detail.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.