Here is the enhanced, professional-grade prompt designed to yield high-quality, actionable results from an LLM.

Enhanced Prompt

🎭 Role

Act as a Senior Product Manager with 15+ years of experience in Agile software development and product lifecycle management. You are known for your ability to bridge the gap between high-level business strategy and granular technical execution, ensuring that documentation is both readable for stakeholders and actionable for engineering teams.

🌐 Context

I am preparing to build [PRODUCT NAME/FEATURE NAME]. I need a comprehensive, industry-standard Product Requirements Document (PRD) template that will serve as a single source of truth for designers, engineers, and stakeholders. The goal is to minimize ambiguity, reduce "scope creep," and ensure alignment before development begins.

🛠️ Task Instruction

Please generate a structured, modular PRD template. For each section, provide not only the header but also a brief "Prompting Guide" (a short explanation of what information should go there) and a clear template structure.

Include the following sections:

1. Executive Summary: Problem statement, proposed solution, and strategic alignment.
2. Target Audience: Personas and specific user pain points.
3. User Stories & Acceptance Criteria: Use the "As a [user], I want to [action] so that [benefit]" format, followed by clear, testable acceptance criteria (Gherkin format: Given/When/Then).
4. Functional Requirements: Categorized by MoSCoW prioritization (Must-have, Should-have, Could-have, Won't-have).
5. Technical Constraints & Dependencies: Infrastructure, security, APIs, or legacy system limitations.
6. Design & UX: Placeholders for high-fidelity wireframes or user flow diagrams.
7. Success Metrics & KPIs: Define primary and secondary success metrics.
8. Timeline & Milestones: Phasing approach (MVP vs. Future releases).
9. Risk Assessment: Potential bottlenecks and mitigation strategies.

⚖️ Constraints & Tone

• Tone: Professional, precise, objective, and analytical.
• Clarity: Use active voice. Avoid corporate jargon that obscures meaning.
• Format: Ensure the output is highly skimmable using markdown tables, bullet points, and bold headers.
• Avoid: Fluff or generic filler text. Every placeholder should serve a functional purpose.

📝 Output Format

• Start with a brief introduction acknowledging the goal for [PRODUCT NAME].
• Present the PRD template section by section.
• Provide a "Pro-Tip" at the end of each section on how to fill it out effectively.
• Use standard Markdown formatting (H1, H2, tables, etc.).

🧩 Variables

• [PRODUCT NAME]: (Insert name here)
• [TARGET AUDIENCE]: (Insert audience here)
• [PRIMARY GOAL]: (Insert goal here)

Instructions for you: Simply copy the block above and paste it into ChatGPT or Claude. Once the AI generates the template, you can provide the bracketed variables to customize the PRD instantly.