Optional planning questions

Choose only questions whose answers affect the current decision. Reuse existing answers and adapt wording to the user; these are prompts, not a required interview sequence or fixed feature-count requirement.

• "What's the name of your product/app? (If undecided, we can brainstorm!)"

• "In one sentence, what problem does it solve?"

• "What's your launch goal? (Examples: '100 users', '$1000 MRR', 'Learn to build apps')"

Level A (Vibe-coder):

• "Who will use your app? What do they do, what frustrates them, how tech-savvy are they?"

• "Tell me the user journey story: [User] has problem X, discovers your app, does Y, now they're happy because Z"

• "What are the 3-5 MUST-have features for launch? Absolute essentials only!"

• "What features are you intentionally saving for version 2?"

• "How will you know it's working? Pick 1-2 metrics: signups, daily users, tasks completed, or feedback score?"

• "Describe the vibe in 3-5 words (e.g., 'Clean, fast, professional' or 'Fun, colorful, friendly')"

• "Any constraints? Budget, timeline, performance, security, platform needs?"

• "Will the product include AI features, ChatGPT/MCP surfaces, internal agents, local/private AI, or automation? If yes, what can AI read/write, which actions require explicit confirmation, and what eval/telemetry evidence is required?"

Level B (Developer):

• "Define your target audience: Primary persona, secondary personas, jobs to be done"

• "Write 3-5 user stories: 'As a [user], I want to [action] so that [benefit]'"

• "List features with MoSCoW: Must have (3-5), Should have (2-3), Could have (2-3), Won't have"

• "Define success metrics: Activation, Engagement, Retention, Revenue (with targets)"

• "Technical/UX requirements: Performance, accessibility, platform support, security, scalability"

• "Risk assessment: Technical, market, and execution risks"

• "Business model and constraints: Monetization, budget, timeline, compliance"

• "AI/automation scope: in-app AI, internal automation, ChatGPT/MCP, local/private AI, provider strategy, data boundaries, retention/training setting to verify, structured outputs, human confirmation rules, telemetry, and eval scenarios"

Level C (In-Between):

• "Who are your users? Primary type, main problem, current solutions they use"

• "Walk through the main user flow: Arrives because..., First sees..., Core action..., Value received..."

• "What 3-5 features must be in v1? For each: name, what it does, why essential"

• "What are you NOT building yet? List v2 features and why they can wait"

• "How will you measure success? Short term (1 month) and medium term (3 months)"

• "Design/UX: Visual style, key screens, mobile responsive?"

• "Constraints: Budget, timeline, non-functional requirements, tech preferences"

• "Does v1 include product AI, AI-facing tools, ChatGPT/MCP, admin agents, local/private AI, or only AI-assisted development?"