Workspace / MVP Worksheet
One product-building system. Choose the pace that fits.
Define, scope, position, design, and build — with AI.
3 ways to use it.
Fill this out to define your product.
Who is this for? Be specific.
What are they trying to do?
What’s the biggest friction?
What is the smallest useful version that solves this?
How will you know if it’s working?
A backlog is your build list, in order. Name the one action your product does, then rank everything else by how close it sits to that action.
My product lets my user
Write it in three lines, so anyone gets it in 30 seconds. Then compress it into one sentence.
Prompt 1 builds the clickable prototype. Prompt 2 maps that flow. Save the link, the file, and the Mermaid chart here so they travel with this worksheet.
Using my MVP scope as the source of truth, build a clickable prototype of the Tier 1 experience as a single HTML file with fake data. No backend, no real accounts or payments. Do not add anything outside Tier 1. Use the minimum screens my user needs to reach the core action, in three taps or fewer, and make it usable without me explaining it. Then give me a one-line note per screen on why it exists, and list any assumptions you made.
Based on the actual prototype I built and the MVP scope above, create a Mermaid flowchart using flowchart TD. The flowchart should reflect what is actually present in the prototype now, even if the prototype has evolved from the original MVP worksheet. Use the MVP worksheet only to identify and annotate which parts of the prototype are: Tier 1 Tier 2 Tier 3 Requirements: - Map the complete experience shown in the prototype from entry through outcomes - One node per real screen - Use the prototype’s actual screen names - Label arrows with the button, link, tap, or user action that causes the transition - Include decision points only where they actually exist in the prototype - Do not invent screens, features, states, or interactions - Annotate each screen or relevant part of the flow as Tier 1, Tier 2, or Tier 3 based on the MVP worksheet - If something exists in the prototype but does not clearly map to a tier in the worksheet, label it Unclassified - Put every node label in double quotes - Keep brackets and colons out of node labels - Return valid Mermaid code - Render the Mermaid chart so I can see it Do not redesign or correct the prototype. Document the experience that exists.
Choose where you will build, then take Prompt 3 and your Source of Truth with you.
You are my product builder. Build a working web application based on the complete BuildKit I am providing. Here are the BuildKit inputs: 1. My MVP worksheet 2. My design prototype (I will upload the files or share a link) 3. My Mermaid experience flow chart 4. The product requirements below Build the full Tier 1 experience exactly as designed in the prototype and described in the MVP worksheet. Requirements: - Use the design, content, structure, and flow from my prototype - Include all Tier 1 features from the MVP worksheet - Make it a complete, working, interactive web application - Use modern, clean, mobile-friendly design - Use realistic placeholder data where needed - Do not invent Tier 2 or Tier 3 features unless I ask - Keep the scope focused on Tier 1 only - If anything is unclear, ask me before making assumptions Create the project, implement the application, and show me a working version I can test in Lovable.
When you complete all 5 phases, you’ll have everything you need to build.
You’re ready to build when these four things agree.MVP decisions + prototype + flow + Source of Truth