mvp-design-frameworklisted

# mvp-design-framework ## Purpose Stop premature coding. Force five framing questions before any scaffold runs. Output a one-page MVP_SPEC.md the rest of the suite consumes. ## When to trigger Trigger on these user phrases. Match loosely. - "design a new app" - "MVP" - "app idea" - "scope a mobile app" - "feature plan" - "what should this app do" - "help me design" - "design framework" - "I want to build an app" ## Behavior Run the five questions in order. Refuse to proceed to question N+1 until question N has a concrete answer. Generic answers are rejected with a follow-up. After all five answers, write MVP_SPEC.md to the project root and print a summary. ## The five questions, asked verbatim ### Question 1: Core function "What is the one thing this app does that, if removed, would mean the app is no longer the app?" Reject if the answer: - Names more than one capability - Names a technology rather than a user outcome ("uses AI", "has Stripe billing") - Names a feature rather than a function ("dark mode", "social login") The answer is a single user outcome stated as a verb plus object. Example: "logs water intake". Not "tracks hydration with reminders and graphs". ### Question 2: Core loop "What is the action the user takes, and the visual or haptic reward they get, inside thirty seconds of opening the app?" The answer names an input action and a sensory feedback within thirty seconds of cold start. If the feedback is "they see their data", reject and ask wha