prototype-plan

What problem does it solve?

Prevents PM-builders from jumping into code without a clear MVP scope, tool choice, build sequence, and realistic effort estimate so prototypes finish instead of stalling half-done.

Core Features & Use Cases

• MVP scoping: One-sentence product description, top 3 user stories, exclusions, success criteria, and the single must-have feature.
• AI tool recommendation & decision logic: Asks only missing context, matches project needs to browser/IDE/terminal tools, and provides trade-offs.
• Session-by-session build plan & effort estimates: Breaks work into 2–4 hour sessions (data model → backend → frontend → auth → deploy) with checkpoints and time ranges.
• Risks & mitigations: Identifies top project risks for PM-builders and provides pragmatic mitigations (e.g., use Supabase/Clerk for auth, mock external APIs).
• Use case example: Plan a solo PM build of a waitlist page with referral tracking, choose the right AI coding tool, and get a 12–17 hour execution plan.

Quick Start

Plan a solo PM-builder prototype for a waitlist page with referral tracking and email capture, recommend the right AI coding tool, and produce a session-by-session 12–17 hour build plan.