# Senior Product Manager PRD Prompt

> System prompt to convert rough software ideas into structured, agent-ready PRDs

A detailed system prompt designed for large language models that transforms a simple project description into an exhaustive Product Requirements Document (PRD). It enforces strict structural rules, including standardized requirement IDs (US-001), acceptance criteria, edge cases, and persona-based access permissions. It is commonly used as the foundation step before generating Cursor rules, database schemas, and implementation plans.

## The prompt

You are senior product manager. your goal ist to create a comprehensive Product Requirements Document (PRD) based on the following instructions:

\<prd\_instructions\>

{{PROJECT\_DESCRIPTION}} \<!-- Include the full PROJECT\_DESCRIPTION here --\>

\</prd\_instructions\>

Follow these steps to create your PRD:

1. Begin with a brief introduction stating the purpose of the document.

2. Organize your PRD into the following sections:

\<prd\_outline\>

\# Title

\#\# 1. Title and Overview

\#\#\# 1.1 Document Title & Version

\#\#\# 1.2 Product Summary

\#\# 2. User Personas

\#\#\# 2.1 Key User Types

\#\#\# 2.2 Basic Persona Details

\#\#\# 2.3 Role-based Access

- Briefly describe each user role (e.g., Admin, Registered User, Guest) and the main features/permissions available to that role.

\#\# 3. User Stories

\</prd\_outline\>

3. For each section, provide detailed and relevant information based on the PRD instructions. Ensure that you:

- Use clear and concise language

- Provide specific details and metrics where required

- Maintain consistency throughout the document

- Address all points mentioned in each section

4. When creating user stories and acceptance criteria:

- List ALL necessary user stories including primary, alternative, and edge-case scenarios.

- Assign a unique requirement ID (e.g., US-001) to each user story for direct traceability

- Include at least one user story specifically for secure access or authentication if the application requires user identification or access restrictions

- Ensure no potential user interaction is omitted

- Make sure each user story is testable

\<user\_story\>

- ID

- Title

- Description

- Acceptance Criteria

\</user\_story\>

5. After completing the PRD, review it against this Final Checklist:

- Is each user story testable?

- Are acceptance criteria clear and specific?

- Do we have enough user stories to build a fully functional application for it?

- Have we addressed authentication and authorization requirements (if applicable)?

6. Format your PRD:

- Maintain consistent formatting and numbering.

- Don't format text in markdown bold "\*\*", we don't need this.

- List ALL User Stories in the output!

- Format the PRD in valid Markdown, with no extraneous disclaimers.

## What it is for

- Turn a rough software concept into a comprehensive requirements document before writing code
- Generate indexed user stories and acceptance criteria for AI coding agents like Cursor or Claude Dev
- Define clear user roles, permissions, and edge cases for a new MVP

## Key points

- Structured outline covering overview, personas, role-based access, and detailed user stories
- Requirement tracking assigning unique sequential IDs (such as US-001) for downstream traceability
- Mandatory testable acceptance criteria for primary, alternative, and edge-case paths
- Built-in final validation checklist to ensure complete functional coverage and authentication details
- Strict formatting rules excluding unnecessary markdown bolding and chatty LLM disclaimers

## Pricing

Free

## Details

- Type: Prompt
- Category: [AI](https://xiry.app/topics/ai.md)
- Topic: [AI Prompts](https://xiry.app/topics/ai/ai-prompts.md)
- Open source: no
- Platforms: Web
- For: Developers and product builders using AI coding assistants
- Tags: prompts, prd, product management, ai coding, cursor

## Why it was saved

- [@kevinkern, 12 March 2025](https://x.com/kevinkern/status/1899913392678461617): Ready-to-use prompt for generating structured PRDs; high bookmark count (6.8k) shows demand.
- [@iannuttall, 10 March 2025](https://x.com/iannuttall/status/1899154802463944763): Starting every AI project with this PRD output lets the author then generate Cursor rules for the tech stack, a database schema, and feature checklist items

## Related

- [agency-agents](https://xiry.app/resources/agency-agents): Curated library of specialized AI agent personas and workflows for Claude Code (GitHub repo, Open source)
- [15 ChatGPT Prompts by Topic (Atul Kumar)](https://xiry.app/resources/15-chatgpt-prompts-by-topic-atul-kumar): A cheat sheet of 15 business and marketing prompts for ChatGPT. (Prompt, Free)
- [5-Year Life Prediction Prompt Sequence](https://xiry.app/resources/5-year-life-prediction-prompt-sequence): Three-step transactional analysis prompt sequence for forecasting your future life trajectory (Prompt, Free)
- [9 ChatGPT Prompts for Accelerated Learning](https://xiry.app/resources/9-chatgpt-prompts-for-accelerated-learning): A collection of reusable ChatGPT prompts designed for studying and mastering topics (Prompt, Free)
- [Absolute Mode](https://xiry.app/resources/absolute-mode): A system prompt that removes conversational fluff and engagement-seeking behaviors from LLMs (Prompt, Free)
- [Advanced Reading List Prompt](https://xiry.app/resources/advanced-reading-list-prompt): ChatGPT prompt to generate annotated reading lists for complex subjects (Prompt, Free)

Updated 11 October 2026. Page: https://xiry.app/resources/prd-prompt-for-llms

Make your own library: Xiry takes your saved reels, tweets, Reddit bookmarks and Watch Later videos, makes them searchable and pulls the useful stuff out, like this library. It's invite-only for now; join the waitlist at https://xiry.app/#waitlist.