Feature PRD Prompt

Goal

Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.

Review the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.

Output Format

The output should be a complete PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.

PRD Structure

1. Feature Name

A clear, concise, and descriptive name for the feature.

2. Epic

Link to the parent Epic PRD and Architecture documents.

3. Goal

Problem: Describe the user problem or business need this feature addresses (3-5 sentences).
Solution: Explain how this feature solves the problem.
Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?

4. User Personas

Describe the target user(s) for this feature.

5. User Stories

Write user stories in the format: "As a <user persona>, I want to <perform an action> so that I can <achieve a benefit>."
Cover the primary paths and edge cases.

6. Requirements

Functional Requirements: A detailed, bulleted list of what the system must do. Be specific and unambiguous.
Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).

7. Acceptance Criteria

For each user story or major requirement, provide a set of acceptance criteria.
Use a clear format, such as a checklist or Given/When/Then. This will be used to validate that the feature is complete and correct.

8. Out of Scope

Clearly list what is not included in this feature to avoid scope creep.

Context Template

Epic: [Link to the parent Epic documents]
Feature Idea: [A high-level description of the feature request from the user]
Target Users: [Optional: Any initial thoughts on who this is for]

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

88

Quality

81

Clarity

85

Completeness

77

Summary

This skill guides an AI agent to act as an expert Product Manager and generate detailed Product Requirements Documents (PRDs) for new features based on parent Epics. The agent takes a feature request and produces a structured Markdown PRD with sections for goals, user personas, stories, requirements, acceptance criteria, and scope boundaries, saved to a project documentation directory.

Detected Capabilities

file writemarkdown generationstructured documentationuser story creationrequirement analysis

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

create feature prdbreak down epicwrite product requirementsdocument feature scopeuser stories and acceptance criteriaproduct requirements documentfeature specification

Use Cases

Create a detailed PRD for a new feature requested by product stakeholders
Break down a high-level Epic into feature-level requirements for engineering teams
Generate a single source of truth for feature scope and acceptance criteria
Establish clear boundaries between what is included and excluded from a feature delivery
Document user personas, stories, and functional/non-functional requirements in a structured format

Quality Notes

Clear, well-organized PRD template with all essential sections for product requirements
Specific output format and directory structure provided (`/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`)
Detailed instructions for each section with guidance on what to include (Problem/Solution/Impact, functional vs non-functional requirements, etc.)
Encourages clarifying questions when information is incomplete, promoting thoroughness
User story template provided in standard format (As a/I want/So that)
Scope boundary section explicitly defined to prevent scope creep
Context template provided to help users supply necessary information
No destructive operations, no credential access, no network calls — purely document generation
Well-aligned with standard product management practices and tools like Jira, Confluence

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

breakdown-feature-prd