<p>My product helps [target customer] [achieve purpose] using [unique feature or mechanism].</p> <p>Now I need to list the assumptions I’m making about how they use the product, what they expect, when they engage, and what behavior I’m counting on.</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| # | Assumption | Why It Matters |</p>

<p>I have an idea for a product and I want to turn it into a simple, clear product spec. Here&#39;s what I know so far:</p> <p>What it is or does:</p> <p>[briefly explain what your product is or helps with]</p> <p>Who it&#39;s for:</p> <p>[describe the people or businesses you&#39;re building it for]</p> <p>Why it matters:</p> <p>[what’s the main problem it solves or benefit it provides?]</p> <p>Important features (optional):</p> <p>[list a few things you think should be part of the product]</p> <p>Things I&#39;m not building (optional):</p> <p>[list anything you&#39;re intentionally leaving out or not focusing on for now]</p> <p>Take this and return a plain text product spec with the following sections:</p> <p>Product Name: [name it something simple for now]<br> One-Liner: [what it does, for whom, and why]<br> Target User: [who it&#39;s for]<br> Core Problem: [the main pain point it solves]</p> <p>Key Features:</p> <p>Feature 1<br> Feature 2<br> Feature 3</p> <p>User Flow:</p> <p>What happens first<br> What happens next<br> How the user completes their goal</p> <p>Out of Scope:</p> <p>Anything not being built for now</p>

<p>ROLE<br> You are a startup operations expert with deep knowledge of the tools used to build, launch, and grow digital products.</p> <p>GOAL<br> List essential tools a team needs to build, launch, and operate the following product:<br> [Product description: what it does, who it’s for, and how it works]</p> <p>Include tools across categories like development, design, automation, analytics, customer support, and operations.</p> <p>OUTPUT<br> Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:<br> | Category | Tool | What It’s For |</p> <p>GUIDELINES<br> • Include 1 to 3 tools per category<br> • Prioritize proven, widely used tools<br> • Skip fluff and focus on tools that save time or help ship faster</p>

<p>I’m working on a product that helps<br> [target user]<br> [achieve goal or solve a problem]<br> using<br> [unique mechanism or key feature]</p> <p>I want to map out the main steps a user goes through, what they’re trying to achieve at each step, and what challenges they face — so I can decide what features to build first.</p> <p>OUTPUT<br> Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:<br> | Step | User Goal | Key Tasks | Pain Points | Potential Features |</p> <p>NOTES<br> • Include 5 to 7 steps in the journey<br> • Focus on high-level goals, not micro-actions<br> • Keep each entry short and clear</p>

<p>I’m building [product or solution] for [target audience] to help with [problem or goal] using [unique feature, mechanism, or approach].</p> <p>Using this information, dig deep into my idea and approach. Identify any hidden assumptions, unknowns, or uncertainties I might be overlooking. Focus on things that could affect product-market fit, user behavior, adoption, or business model. Return a short analysis in clear, thoughtful language that surfaces 5 to 7 key points I should think about.</p>

<p>I’m building a product for [target audience] who struggle with [the main challenge or frustration].</p> <p>Using this information, rewrite it into a sharp who / struggle / why-now statement. Keep it short and clear so it highlights who the user is, what their struggle is, and why solving it now matters. Make sure the statement flows and reads well.</p>

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, tell me whether this idea is more likely a zero-to-one play (invention, creating something new) or a one-to-n play (scaling or improving something proven). Explain why, and highlight how that framing changes my assumptions, risks, and approach to execution.</p>

<p>My interest area is [industry, theme, or topic, for example AI tools, healthcare, travel, education, social media]</p> <p>Using this, generate 20 intentionally bad, silly, or impractical product or business ideas in this space. They should be exaggerated, funny, or clearly flawed but still loosely related to the industry or theme. The goal is to break patterns, surface overlooked angles, and spark creative thinking.</p> <p>Return the list as plain text with each idea numbered from 1 to 20.</p>

<p>The problem I’m working on is<br> [state the problem in one or two sentences]</p> <p>Using this, break it down into first principles by</p> <p>Stripping away assumptions and restating the problem in its most basic terms<br> Identifying the fundamental truths or constraints that are undeniably valid<br> Rebuilding the logic step by step into a solution approach that is free from unproven assumptions<br> Highlighting how this new framing changes or challenges my original perspective</p> <p>Keep the explanation clear, logical, and structured so I can see both the raw fundamentals and the rebuilt solution logic.</p>

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, write two short paragraphs</p> <p>Paragraph 1: Describe the life of the target audience before using the product. Highlight the struggles, inefficiencies, or frustrations they face.</p> <p>Paragraph 2: Describe their life after using the product. Show how their experience improves, what outcomes they achieve, and why it feels like a meaningful transformation.</p> <p>Keep it simple, relatable, and emotionally engaging.</p>

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, tell me<br> • What existing solutions or workflows this product is unbundling (breaking apart)<br> • What it is rebundling (combining into one place or flow)<br> • The main barriers or frictions for users that this approach removes<br> • Why this framing matters for positioning and go-to-market</p> <p>Keep the output concise and clear so I can quickly see how my product fits into the unbundle vs rebundle story.</p>

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, identify<br> • A narrow, high-pain beachhead use case where adoption is most likely to start<br> • Why this wedge is critical and how it builds credibility or traction<br> • The main reasons users in this wedge would choose my product first over alternatives<br> • How solving this wedge use case creates expansion opportunities into adjacent markets or features</p> <p>Keep the output focused, specific, and actionable so I can clearly see where to start and why it matters.</p>

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, generate 1 to 3 relevant shifts in each PESTLE category that support why now is the right time for this idea</p> <p>Political<br> Economic<br> Social<br> Technological<br> Legal<br> Environmental</p> <p>Keep each shift short, clear, and directly tied to how it enables or accelerates adoption of my product</p>