write-prd-prompt

A prompt that turns a rough app or website idea into a concise product requirements document (PRD) with users, scope, user stories, data model and an MVP build plan, or a website brief with a page list and copy per page. Use when the user wants to plan an app or site, draft a spec, scope an MVP, or turn an idea into requirements before coding.

Version 1.1 · Updated 2026-10-31

View raw SKILL.md

Install in Claude Code, Cursor or Codex (optional)

Only for AI coding tools that read skill folders. Run one line in a terminal, in your project folder. It downloads this skill's text files from TheSkillVault and nothing else; you can read them first with “View raw SKILL.md”.

Claude Code (all your projects)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/write-prd-prompt/raw' -o ~/'.claude/skills/write-prd-prompt/SKILL.md'

Cursor (this project)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/write-prd-prompt/raw' -o '.cursor/skills/write-prd-prompt/SKILL.md'

Codex and other Agent Skills tools (this project)

curl -fsSL --create-dirs 'https://theskillvault.ai/api/skills/write-prd-prompt/raw' -o '.agents/skills/write-prd-prompt/SKILL.md'

Or connect the whole library over MCP

Add TheSkillVault to Cursor or add this to your app's MCP settings (read-only; help):

{
  "mcpServers": {
    "theskillvault": {
      "url": "https://theskillvault.ai/mcp"
    }
  }
}

Write a PRD (prompt)

When to use

Before the first line of code on a new app or a big feature.

Prompt

You are a senior product manager. Turn my idea into a one-page PRD I can hand to an AI coding agent.

Idea: {{IDEA}}
Target users: {{USERS or "infer and state your assumption"}}
Constraints: {{STACK, BUDGET, DEADLINE}}

Ask me up to 5 clarifying questions first if anything critical is missing. Then write:
1. Problem and goal (3 sentences max)
2. Users and top 3 jobs-to-be-done
3. MVP scope: must-have / not-now lists
4. User stories with acceptance criteria (Given/When/Then)
5. Data model (entities, key fields, relations)
6. Screens and main flows
7. Risks and open questions
8. Build plan: 5-8 small, independently testable steps in order
Keep it under 800 words. No marketing language.

Website mode

Use this block instead when the thing you are building is a small-business or marketing website. Save the answer as docs/website-brief.md in the project: the next steps of the Standard Website path read it from there.

You are a website planner for small businesses. Turn my business idea into a one-page website brief I can hand to an AI coding agent.

Business: {{WHAT YOU SELL OR DO, AND WHERE}}
Who it is for: {{CUSTOMERS or "infer and state your assumption"}}
What visitors must do: {{ONE MAIN ACTION, e.g. "send an enquiry", "book a call"}}

Ask me up to 5 clarifying questions first if anything critical is missing. Then write, in Markdown:
1. Goal (2 sentences) and audience
2. The one main call to action (button text and where it goes, usually /contact)
3. Page list: Home, About, Services, Contact, Privacy (add or remove pages only if I asked)
4. For each page: its sections in order, a draft headline, and 2-4 sentences of draft copy
5. Brand notes: colours, fonts, logo file, tone of voice (say "none yet" if unknown)
6. Business details for the footer and search engines: business name, address or service area, phone, email, opening hours
7. What the contact form should ask for, and nothing more
Keep it under 900 words. Plain words, no jargon. Start the file with the heading "# Website brief".

How to adapt

Building a website? Use Website mode and save the answer as docs/website-brief.md.
Paste the PRD into docs/PRD.md and tell the coding agent to follow the build plan one step at a time.
For a feature (not an app), replace sections 2 and 6 with "affected screens and APIs".

Example prompt

"Help me plan a booking app for my cleaning business before we build it."

Licence: CC BY 4.0. Attribution when you reuse it: From TheSkillVault, https://theskillvault.ai, CC BY 4.0