prototype-plan

Plans MVP builds with AI coding tool recommendations and session-by-session estimates.

5|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tarunccet/pm-skills --skill prototype-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype-plan
Source: https://github.com/tarunccet/pm-skills/tree/main/pm-vibe-coding/skills/prototype-plan
Command: npx skills add https://github.com/tarunccet/pm-skills --skill prototype-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about prototype-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan an AI-assisted MVP prototype without stalling halfway?

To plan an MVP prototype without stalling, define a one-sentence scope, identify the must-have feature, and sequence 2-4 hour build sessions with realistic effort estimates. This approach prevents half-done prototypes by providing clear checkpoints and time ranges.

What is the best way to scope an MVP for a solo PM-builder using AI coding tools?

Scoping an MVP for a solo PM-builder involves creating a one-sentence product description, selecting top user stories, defining exclusions, and establishing success criteria. This process identifies the single must-have feature to focus AI coding efforts effectively.

How do I choose the right AI coding tool for my prototype build?

Choosing the right AI coding tool requires evaluating your project needs, technical comfort, backend requirements, and existing tools. Matching these inputs allows you to select appropriate browser, IDE, or terminal tools while understanding the trade-offs of each option.

Can I get a time estimate for building a full-stack MVP with AI assistants?

You can get a time estimate for building a full-stack MVP with AI assistants by breaking work into sequential sessions covering data model, backend, frontend, auth, and deployment. Each phase receives specific time ranges, typically producing a 12-17 hour execution plan for simple projects.

What are common risks when building an MVP prototype as a solo PM-builder?

Common risks when building an MVP prototype as a solo PM-builder include authentication complexity and external API dependencies. Mitigations involve using managed services like Supabase or Clerk for auth and mocking external APIs to maintain development velocity.