4 Prompts for Builders: From Idea to Product Spec and Landing Page

A structured set of prompts that take you from a raw idea all the way to a functional spec and landing page. Use them sequentially — each one builds on the previous output.

Prompt 1 — Product Brief

I want to build a product. Here’s my idea:

[PROJECT DESCRIPTION — write a few sentences: what it is, who it’s for, what problem it solves, roughly how it should work]

Help me create an initial product brief.

BUT BEFORE YOU WRITE — ask me 5-10 questions about things I might not have thought about, including:

• Who exactly is my user and what are their pain points?
• What do they do TODAY to solve this problem (without my product)?
• What must be in the first version (v1), and what can wait?
• Is this a tool for me/my company, or a SaaS for many customers?
• Scale: how many users at launch? Tens, hundreds, thousands?
• Decisions that are hard to reverse later (architecture, data model)
• How will I know the MVP works / succeeded?
• Potential problems and risks
• Features I might not have thought of, or elements that require important decisions

After my answers, create a brief (in markdown format) with this structure:

1. PROJECT NAME (working title)
2. PROBLEM (1-3 sentences: what’s wrong, what hurts the user)
3. USER PERSONA (Who is the main user? Context, situation, pain points, what they use today instead. If there are multiple roles — describe each.)
4. VALUE PROPOSITION (1-2 sentences: why would someone use this?)
5. KEY MVP FEATURES (5-7 features — only what MUST be in v1)
6. WHAT THIS IS NOT (4-6 things you consciously DON’T build in v1)
7. SUCCESS CRITERIA (2-3 measurable success criteria)
8. INSPIRATIONS / REFERENCES (optional)

Prompt 2 — Functional Specification

Based on the brief below, create a functional specification. The brief says WHAT I’m building. The specification says HOW IT WORKS from the user’s perspective.

BEFORE YOU WRITE — ask me questions grouped into these categories:

ROLES & PERMISSIONS:

• What are the user roles? (e.g., admin, user, viewer)
• What can each role do, and what can they NOT do?
• Who creates accounts? What does first contact with the app look like?

USER FLOWS:

• What is the most important flow? (core flow — step by step)
• What other flows are critical for v1?

BUSINESS RULES:

• What happens when [key situations]? (overdue, missing data, duplicate)
• What are the limits? (how many items, how long, how big)
• What is reversible, and what is irreversible?

SUCCESS CONDITIONS:

• How do you know a feature works correctly?
• What scenarios must pass for you to consider a feature “done”?

ADDITIONAL QUESTIONS:

• Anything worth detailing or that was unclear from the brief
• Ideas for important new features

After my answers, create a specification with these sections:

1. USER ROLES (list of roles with permissions)

2. USER STORIES WITH ACCEPTANCE CRITERIA

   “As [role] I want [action] so that [benefit]”

   GIVEN [context] WHEN [action] THEN [result]

   Priority: P0 (must have) / P1 (should have) / P2 (nice to have)

3. USER FLOWS (step by step for 2-3 most important paths)

4. BUSINESS RULES (“If [condition] then [system behavior]”)

[PASTE YOUR BRIEF HERE]

PRO TIP: For advanced users — do the same in 2 separate chats and merge the results. Two different AI “perspectives” give a fuller specification.

Prompt 3 — MVP vs V2 Split

Below is the functional specification of my app. Prepare it for pasting into Replit Agent.

STEP 1: PRIORITIZATION (before you write anything)

Analyze the specification and propose a MoSCoW prioritization:

• Must Have — without this the app doesn’t work
• Should Have — important, but MVP survives without it
• Could Have — nice additions
• Won’t Have — consciously deferred

Present me a table with the proposed split and ASK if I agree. Wait for my answer. Only after approval, proceed to step 2.

STEP 2: GENERATE SPECIFICATION

Based on the approved split:

1. SPLIT INTO MVP AND V2: MVP = Must Have (+ Should Have), V2 = rest
2. ADD A SECTION AT THE TOP: MVP — build ONLY this […], V2 — do NOT build now […]
3. KEEP the rest of the specification unchanged. For V2 user stories, add: V2 — DO NOT BUILD NOW
4. At the end, add: “Build ONLY features from the MVP section.”

FORMAT: Return a ready-to-copy specification — no explanations.

[PASTE YOUR FUNCTIONAL SPECIFICATION HERE]

Prompt 4 — Landing Page

I’m the creator of the app. Based on my product brief, generate a READY-TO-PASTE prompt for Lovable or Replit Design Mode that builds a complete landing page.

Your output is ONE READY PROMPT — with marketing copy and design description.

THE PROMPT YOU GENERATE should contain:

1. Design Description

Visual style (modern, minimalist), primary color and CTA color, clean sans-serif, mobile first, visual inspirations (1-2 well-known SaaS sites).

2. Page Structure with Ready Copy

• NAVIGATION: Logo + CTA button
• HERO: Headline (max 8 words, BENEFIT not feature) + subheadline + CTA + social proof
• SOCIAL PROOF BAR + PROBLEM + SOLUTION
• FEATURES (grid): 3-4 features with BENEFIT descriptions
• HOW IT WORKS (3 steps) + TESTIMONIALS (2-3 cards)
• FAQ (accordion, 4-5 questions) + FINAL CTA + FOOTER

3. Tool Rules

• One CTA color across the entire page, CTA button repeats multiple times
• Smooth scroll + subtle animations (fade-in on scroll)
• Mobile: hamburger menu, vertical stack, readable buttons

COPYWRITING RULES:

• Write in BENEFIT language, not features (NOT “has admin panel” → YES “manage everything from one place”)
• Tone: professional but human, zero corporate jargon
• Keep it short — a landing page is not documentation

FORMAT: Return ONLY the ready-to-copy prompt — no explanations.

[PASTE YOUR BRIEF FROM STEP 2 OR SPEC FROM STEP 3]