What this prompt does
This prompt casts the model as a serial side-project builder that takes you from idea to launch efficiently. You describe your [project_idea] and constraints — [time_available], [budget], [team_size], and [tech_skills] — and it returns a seven-phase launch plan: validation, MVP scoping, tech-stack selection, a build sprint, a pre-launch checklist, a launch-day playbook, and a 30-day post-launch plan.
The structure enforces the discipline most side projects skip: validate before building, then cut scope ruthlessly. Phase one is a validation checklist plus a customer-interview script, with a [validation_target] of email signups to hit before writing code. Phase two splits features into must-have launch blockers and cut-from-MVP, with build-time estimates. Phase three recommends a stack based on your [tech_skills] with the rule "use boring technology," and [additional_layer] lets you pose a specific decision like which AI integration to use. The later phases turn launch into an hour-by-hour playbook across your chosen [launch_platforms].
When to use it
- When you have a side-project idea and keep getting stuck before shipping.
- To force real validation (interviews, a landing page, signups) before you write code.
- When you tend to over-build and need help cutting an MVP to its essentials.
- To choose a fast, familiar tech stack instead of learning something new mid-project.
- When you want an hour-by-hour launch-day plan and a 30-day post-launch roadmap.
Example output
You get a seven-phase plan: a validation checklist with a customer-interview script and a signup target, an MVP scope split into must-have (with build-time estimates) and cut-from-MVP tables, a tech-stack table recommending frontend, backend, database, hosting, auth, and payments with alternatives, a week-by-week build sprint, a pre-launch checklist (legal pages, transactional emails, error monitoring, analytics, beta users), an hour-by-hour launch-day playbook for your platforms, and a 30-day post-launch plan ending in a double-down/pivot/sunset decision.
Pro tips
- Describe
[project_idea]in one clear sentence; the validation phase tests whether you can articulate the value as "I help who do what so they can benefit." - Set
[time_available]and[budget]realistically — the build sprint and stack recommendations (free tiers, boring tech) are sized to your real constraints. - List your true
[tech_skills]so the stack advice leans on what you already know; the plan's core rule is that a side project isn't where you learn a new framework. - Take the validation phase seriously — hitting the
[validation_target]signups before building is the discipline that prevents wasted weeks. - Use
[additional_layer]to resolve a real architectural decision, like OpenAI API versus a local model, inside the stack table. - Set
[launch_platforms]to where your audience actually is; the launch-day playbook and announcement drafts are tailored to those channels.
