COPYYou are a world-class product strategist. I have a business idea I want to explore. Help me structure it by asking me 10 sharp questions — one at a time — that will uncover: 1. The exact problem being solved 2. Who experiences this problem most acutely 3. How they currently solve it (workarounds) 4. What makes this idea unique 5. The scale of the opportunity After my answers, output a structured IDEA BRIEF in this format: - Problem Statement (1 sentence) - Target User (1 sentence) - Proposed Solution (2 sentences) - Unique Angle (1 sentence) - Biggest Risk (1 sentence) - Opportunity Size Guess (rough) My idea: [PASTE YOUR RAW IDEA HERE]

COPYYou are a market research analyst. Use web search to research the market for: Product Category: [CATEGORY] Target Geography: [GEOGRAPHY] Target User: [USER TYPE] Find and calculate: 1. TAM — Total Addressable Market (cite sources) 2. SAM — Serviceable Addressable Market (realistic subset) 3. SOM — Serviceable Obtainable Market (year 1–3 target) 4. Market growth rate (CAGR) 5. Top 5 existing players and their funding/revenue 6. Market gaps that are underserved Output as a clean table + 3-sentence market narrative.

COPYYou are a competitive intelligence expert. Research competitors for: Idea: [IDEA] Find the top 8 competitors (direct + indirect). For each, output: | Competitor | Founded | Funding | Pricing | Target User | Key Feature | Weakness | Then: 1. Draw a 2x2 positioning map (Price vs Feature Depth) 2. Identify the positioning gap where our product can win 3. List 3 features competitors all have (table stakes) 4. List 3 features no competitor offers well (our opportunity) End with: "Our defensible position should be..."

COPYYou are a user research expert. Create 3 detailed Ideal Customer Profiles for: Product: [PRODUCT] Problem solved: [PROBLEM] For each persona, define: - Name, Age, Job Title, Company Size - Daily workflow (relevant parts) - Top 3 frustrations related to our problem - How they currently solve it (tools, workarounds) - What a 10x better solution would mean for them - Willingness to pay (monthly, annual) - Where they hang out online (channels to reach them) - What they'd Google to find us - Emotional buying trigger ("I'd pay for this the day it could...") Format each as a persona card. Then rank: which persona should we build for first and why?

COPYScore this business idea across 8 dimensions. Use the context below. Idea: [IDEA BRIEF FROM V-01] Market research: [PASTE V-02 OUTPUT] Founders: [SKILLS / TEAM] Capital available: [BUDGET] Timeline goal: [TIMELINE] Score each 1–10 with a 1-line rationale: 1. Market Size (is there enough demand?) 2. Problem Urgency (do people need this now?) 3. Technical Feasibility (can it be built with available resources?) 4. Capital Efficiency (can we validate cheaply?) 5. Competitive Moat (can we defend against copycats?) 6. Team-Market Fit (are we the right people for this?) 7. Revenue Clarity (is the path to $1 obvious?) 8. Timing (is the market ready?) Total score: /80. Verdict: GO / NO-GO / PIVOT with reasoning.

COPYYou are a senior Product Manager at a top-tier startup. Using this context: - Idea Brief: [V-01 OUTPUT] - Primary Persona: [V-04 PERSONA 1] - Feasibility Score: [V-05 OUTPUT] Write a complete PRD with these sections: ## 1. Product Vision One sentence that defines the north star. ## 2. Problem Statement The exact problem, who has it, and what it costs them today. ## 3. Goals & Success Metrics 3 business goals + KPIs for each (measurable, time-bound). ## 4. User Stories Top 10 user stories in format: "As a [persona], I want to [action] so that [outcome]." Include acceptance criteria for each. ## 5. Feature List Organize as: Must Have / Should Have / Nice to Have (MoSCoW). For each feature: name, description, user benefit, complexity estimate (S/M/L). ## 6. Out of Scope 5 things we explicitly will NOT build in v1. ## 7. Open Questions Top 5 things we need to validate with users before building. ## 8. Launch Criteria What must be true for us to call this MVP "launched"?

COPYYou are a lean startup expert. Your job is to REDUCE scope, not add to it. Given this PRD: [P-01 OUTPUT] Answer these questions ruthlessly: 1. If we could only ship ONE feature — which one delivers the core value promise? 2. For each Must-Have feature: what is the 80% version that takes 20% of the time? 3. What assumptions are we making that we haven't tested yet? 4. What is the riskiest assumption? How do we test it in 1 week without building anything? 5. Draw a "walking skeleton" — the thinnest possible end-to-end flow that a real user could use. Output: MVP Feature Set (max 5 features), Timeline estimate, and ONE metric that proves the MVP worked.

COPYCreate a 3-phase product roadmap for [PRODUCT]. Context: [PRD + MVP SCOPE] Team size: [TEAM] Timeline: [MONTHS] Phase 1 — NOW (Month 1–2): MVP. Survive. Phase 2 — NEXT (Month 3–5): Retention + first revenue. Phase 3 — LATER (Month 6–12): Growth + moat. For each phase: - Features shipped - Key metric to move - What we learn - Resource requirement - Go/No-go criteria to advance to next phase Format as a table. Add a risk column for each phase.

COPYGenerate complete user stories for this feature: Feature: [FEATURE NAME] Product: [PRODUCT] Primary User: [PERSONA] For each story: - User story: "As a [role], I want [action] so that [outcome]" - Acceptance criteria (Given / When / Then format) - Edge cases to handle - Out of scope for this story - UI/UX considerations - API needed (if any) - Estimated complexity: XS / S / M / L / XL Generate: 1 happy path story + 2 edge case stories + 1 error state story.

COPYScore and rank this feature backlog using the RICE framework. Product context: [PRODUCT + USERS] Features to score: [LIST ALL FEATURES] For each feature, estimate: - Reach: How many users affected per quarter? (number) - Impact: How much does it move our core metric? (0.25 / 0.5 / 1 / 2 / 3) - Confidence: How sure are we? (%) - Effort: Person-weeks to build RICE Score = (Reach × Impact × Confidence) / Effort Output as a ranked table. Flag the top 3 as "Sprint 1" and explain why they're the right bet.

COPYYou are a senior CTO advisor. Recommend a tech stack for: Product type: [WEB APP / MOBILE / API / SAAS] Expected users (year 1): [NUMBER] Team skills: [LANGUAGES / FRAMEWORKS KNOWN] Budget: [MONTHLY INFRA BUDGET] Timeline to MVP: [WEEKS] Core features: [TOP 5 FEATURES] Recommend: 1. Frontend framework + why 2. Backend framework + why 3. Database (primary + cache) + why 4. Auth solution + why 5. File storage + why 6. Email service + why 7. Payments + why 8. Hosting/deploy + why 9. Monitoring + why 10. AI/LLM integration + why For each: free tier available? Monthly cost at 1000 users? Alternative if this fails? Final output: starter repo structure + estimated monthly cost at 3 scales (100 / 1K / 10K users).

COPYDesign the system architecture for: Product: [PRODUCT] Stack: [T-01 OUTPUT] Core features: [TOP FEATURES] Output: 1. Component diagram (describe all services and how they connect) 2. Data flow: trace a user's full journey from login to core action 3. API structure: list all endpoints (method, path, purpose, auth required) 4. Database tables: name, key fields, relationships 5. Third-party integrations and their role 6. Security boundaries (what is public vs private) 7. Caching strategy 8. Failure points and fallback plan for each Format the API list as a table. Format DB tables as schema definitions.

COPYDesign a complete database schema for: Product: [PRODUCT] Database: [POSTGRES / MYSQL / MONGODB] Core entities: [LIST MAIN DATA OBJECTS] For each table: - Table name - All columns with types, constraints, defaults - Primary key, foreign keys, indexes - Relationships (1:1, 1:many, many:many) Rules: - Normalize to 3NF minimum - Include: created_at, updated_at, soft delete (deleted_at) on all main tables - Multi-tenancy support (if SaaS): org_id on all tenant-scoped tables - Include Row Level Security policies if using Supabase Output as SQL CREATE TABLE statements + an ERD description. Flag any design decisions that involve tradeoffs.

COPYDesign the AI integration layer for: Product: [PRODUCT] AI model to use: [Claude Sonnet / GPT-4o / Gemini] AI features needed: [LIST AI FEATURES] Design: 1. Prompt architecture (system prompt structure, context injection, user input handling) 2. Context window management (what goes in, what gets summarized, what is cut) 3. Streaming vs batch (which features need streaming output?) 4. Cost control (estimate tokens per feature, monthly cost at 1K users) 5. Caching strategy (what AI outputs can be cached?) 6. Fallback plan (if API is down or rate limited) 7. Evaluation loop (how do we know if AI responses are good?) 8. Safety filters (what outputs do we block or review?) Output the system prompt template for the core AI feature. Include [VARIABLES] in caps.

COPYPerform a security review for: Product: [PRODUCT] Stack: [STACK] Data stored: [USER DATA TYPES] Review and give pass/fail + fix for each: Auth & Access: □ JWT expiry + refresh strategy □ Rate limiting on auth endpoints □ Password hashing (bcrypt/argon2) □ OAuth token storage □ RBAC / permissions model Data Security: □ SQL injection prevention □ XSS prevention □ CSRF protection □ Sensitive data encryption at rest □ Secure API key management □ PII data handling compliance Infrastructure: □ HTTPS everywhere □ Env vars vs hardcoded secrets □ Dependency vulnerability scan □ Logging (no PII in logs) □ Backup strategy Output: Priority-ordered fix list with code snippets for critical issues.

COPYYou are a monetization strategist. Design the revenue model for: Product: [PRODUCT] Personas: [ICP 1, ICP 2, ICP 3] Competitors' pricing: [FROM V-02] Our differentiation: [UNIQUE ANGLE] Design: 1. Primary revenue model (subscription / usage / marketplace / freemium / one-time) 2. Pricing tiers (3 recommended): name, price, what's included, who it's for 3. Free tier scope (what's free and why — acquisition or goodwill?) 4. Upsell triggers (what feature makes users upgrade?) 5. Annual vs monthly discount strategy 6. Enterprise/custom tier criteria 7. Expansion revenue opportunities (seats, usage, add-ons) Calculate unit economics: - ARPU target (average revenue per user) - Target gross margin % - Payback period assumption - MRR needed to cover $[MONTHLY COSTS] in operating costs Output a pricing page copy draft for each tier.

COPYYou are a GTM expert. Create a go-to-market plan for: Product: [PRODUCT] Primary ICP: [PERSONA 1] Budget: [MARKETING BUDGET] Goal: First 100 paying customers in [TIMEFRAME] Design: 1. Launch channels (rank by: low cost, fast feedback, right audience) 2. Week 1–2: Pre-launch (waitlist, community seeding, beta recruitment) 3. Week 3–4: Launch (Product Hunt, HN, Reddit, newsletters, cold outreach) 4. Month 2–3: Growth (content, SEO foundations, partnership, paid experiments) For each channel: - Platform + specific community/subreddit/newsletter - Message/angle that will resonate - Expected CAC - Expected volume Cold outreach template (50-word max email that gets replies): Landing page headline options (3 variants A/B test): First 10 beta users acquisition plan:

COPYBuild a 12-month financial model for: Product: [PRODUCT] Pricing: [TIERS + PRICES FROM B-01] Monthly costs: [INFRA + TEAM + TOOLS] Growth assumption: [% MoM USER GROWTH] Churn assumption: [MONTHLY CHURN %] Free-to-paid conversion: [%] Output a month-by-month table: | Month | New Users | Paid Users | MRR | Churn | Net MRR | Costs | Profit/Loss | Key milestones to highlight: - Month we hit default alive (revenue > costs) - Month we hit $1K MRR / $10K MRR - Total capital needed before profitability Assumptions section: list every assumption made — flag the 3 most dangerous ones.

COPYYou are a brand strategist. Create the messaging framework for: Product: [PRODUCT] Category: [WHAT WE DO] Primary user: [ICP] Key benefit: [TOP VALUE PROP] Competitors: [MAIN ALTERNATIVES] Create: 1. Positioning statement: "For [user] who [problem], [product] is the [category] that [key benefit]. Unlike [competitor], we [key differentiator]." 2. Tagline options (5 variants, 3–7 words each) 3. One-liner (25 words max) for cold outreach 4. Hero headline for landing page (pain-led vs outcome-led variants) 5. Three messaging pillars (core claims we can prove) 6. Proof points for each pillar (stats, case studies, testimonials) 7. Words to avoid (category clichés that make us sound like everyone else) 8. Tone of voice: 3 adjectives, 1 brand we sound like

COPYYou are a senior full-stack engineer. Build this feature completely: Feature: [FEATURE NAME] Stack: [STACK FROM T-01] User story: [FROM P-04] DB schema: [RELEVANT TABLES FROM T-03] Build in this order: 1. DB migration (SQL) 2. API route(s) — full code with error handling 3. Input validation schema (Zod / Joi) 4. Frontend component — full code, responsive, accessible 5. Loading + error + empty states for the UI 6. Unit test for the core logic 7. Integration test for the API route Rules: - TypeScript only - Handle all error cases explicitly (no silent failures) - Include JSDoc comments on public functions - No TODO comments — write the actual implementation - Production-ready: auth check, rate limit, input sanitize Output each file as a separate code block with the file path as a comment.

COPYBuild a complete authentication system for: Stack: [FRAMEWORK] Auth provider: [Supabase Auth / Clerk / NextAuth / Custom JWT] OAuth providers needed: [Google / GitHub / etc] User roles needed: [admin / user / etc] Build: 1. Sign up flow (email + OAuth) with email verification 2. Sign in flow with remember me 3. Password reset flow 4. Session management + JWT refresh 5. Auth middleware (protect routes) 6. Role-based access control (RBAC) setup 7. "Magic link" login option Include: - Database tables for users, sessions, roles - All API routes with validation - Frontend forms with client-side validation - Error handling for all auth failure cases - Rate limiting on auth endpoints

COPYIntegrate Stripe payments for: Product: [PRODUCT] Payment type: [SUBSCRIPTION / ONE-TIME / USAGE-BASED] Pricing tiers: [FROM B-01] Stack: [FRAMEWORK] Build: 1. Stripe product + price setup (CLI commands) 2. Checkout session creation API route 3. Success + cancel redirect handling 4. Webhook handler for: payment_intent.succeeded, customer.subscription.*, invoice.payment_failed 5. Customer portal integration (manage subscription) 6. Subscription status check middleware 7. DB schema: subscriptions, payments tables 8. Frontend: pricing page, upgrade flow, billing section Include: test mode setup, webhook local testing with Stripe CLI, error handling for failed payments.

COPYBuild a high-converting landing page for: Product: [PRODUCT] Positioning: [FROM B-04 — headline, tagline, pillars] Primary CTA: [SIGN UP FREE / REQUEST DEMO / JOIN WAITLIST] Social proof: [TESTIMONIALS / USER COUNT / LOGOS] Build in Next.js + Tailwind with these sections: 1. Hero: headline, subheadline, CTA, hero image/mockup area 2. Social proof bar (logos or user count) 3. Problem section (pain before our solution) 4. Solution section (3 key features with icons) 5. How it works (3-step visual flow) 6. Testimonials (3 cards) 7. Pricing section (3 tiers) 8. FAQ (5 questions) 9. Final CTA + footer SEO: Add meta tags, OG image placeholder, semantic HTML. Performance: lazy load images, no layout shift, Lighthouse 90+.

COPYSet up the DevOps infrastructure for: Stack: [STACK] Hosting: [Vercel / Railway / Render / AWS / GCP] DB: [DATABASE + HOSTING] Set up: 1. Environment management (.env.local, .env.production, secrets) 2. GitHub Actions CI pipeline: lint → test → build → deploy 3. Preview deployments for PRs 4. Production deployment with zero-downtime 5. Database migration strategy (auto-run in CI vs manual) 6. Error monitoring setup (Sentry — free tier config) 7. Uptime monitoring (Better Uptime / UptimeRobot — free) 8. Log aggregation setup 9. Backup strategy for database 10. Custom domain + SSL setup Output: all config files, GitHub Actions YAML, and Dockerfile if needed.

COPYYou are a product discovery expert conducting the first session with a new client. Their raw idea: [CLIENT'S WORDS — PASTE EXACTLY AS THEY SAID IT] Ask these questions in a warm, conversational way — not as a list. Explore one at a time, go deep, don't rush: 1. Tell me about the moment you first thought of this. What were you frustrated about? 2. Who do you imagine using this first? Do you know them personally? 3. Have you talked to potential users yet? What did they say? 4. What have you already tried building or testing? 5. What does success look like in 12 months? (revenue, users, impact) 6. What would make you declare this a failure and shut it down? 7. Who else is working on this with you? 8. What's your biggest fear about this project? 9. What resources do you have? (time, money, team, connections) 10. What do you need from me specifically? After all answers: output the Client Brief document to be passed into Prompt V-01.

COPYGenerate a weekly status update email for my client. Week number: [N] What we planned: [PASTE LAST WEEK'S PLAN] What we actually did: [BULLET LIST OF COMPLETED ITEMS] Blockers encountered: [LIST] Next week plan: [BULLET LIST] Key decision needed from client: [IF ANY] Current status: [ON TRACK / AT RISK / DELAYED] Write a professional but warm email that: - Opens with 1 positive highlight - Is honest about blockers without causing panic - Clearly states what needs client input - Closes with a clear ask for the week - Is max 200 words Also generate: a 3-slide deck outline (title, progress, next week) for async Loom update.

COPYPrepare a milestone demo script for: Milestone: [MILESTONE NAME, e.g. "MVP Demo - Week 4"] What was built: [FEATURE LIST] What still has gaps: [HONEST LIST] Client expectations set: [WHAT WE PROMISED] Next milestone: [WHAT COMES NEXT] Write: 1. Demo flow (step-by-step what to show and in what order) 2. Talking points for each feature (benefit-first, not tech-first) 3. How to handle the gaps gracefully (frame as "by design" or "in backlog") 4. 5 questions the client will likely ask — and ideal answers for each 5. Call-to-action at end of demo (what decision do we need from them?) 6. Follow-up email template (send within 1 hour of demo)

COPYA client wants to add a new feature mid-project. Help me respond. Original scope: [ORIGINAL FEATURES] New request: [WHAT CLIENT WANTS TO ADD] Current timeline: [WEEKS REMAINING] Impact: [ROUGH ESTIMATE OF ADDED WORK] Write: 1. A professional email acknowledging the request positively 2. Analysis: what is the actual impact on timeline + cost? 3. Three options to offer the client: a. Add it — here's the cost + timeline impact b. Add it in Phase 2 — here's when c. Replace something — what to cut instead 4. Recommended option with rationale 5. A scope change document template they can sign off on Keep the tone: collaborative, not defensive. We're on their side.

COPYAnalyze this batch of user feedback and turn it into action: Product: [PRODUCT] Feedback collected: [PASTE ALL RAW FEEDBACK — INTERVIEWS, EMAILS, REVIEWS] Current version: [WHAT'S LIVE] Analyze: 1. Cluster feedback into themes (group similar issues) 2. Frequency + sentiment for each theme 3. Distinguish: bug reports vs feature requests vs UX confusion vs missing features 4. Quote the most impactful individual piece of feedback (the one that should keep us up at night) 5. Prioritized action list: Critical / High / Medium / Low 6. Feature requests to add to backlog with user quote as rationale 7. Quick wins (can be fixed in < 1 day) — ship these first 8. What the data tells us about our ICP fit (are the right people using this?)