Feature PRD Prompt
OfficialFreeGenerate detailed Product Requirements Documents from Epics.
Free · Opens the source repo
What Feature PRD Prompt does
The Feature PRD Prompt skill is designed for product managers and teams working on large-scale SaaS platforms. It helps users create comprehensive Product Requirements Documents (PRDs) based on high-level features or enablers outlined in Epics. By acting as an expert product manager, this skill ensures that all necessary details are captured, providing a single source of truth for engineering teams.
When using this skill, users begin by providing information about a new feature and its parent Epic. The skill then prompts for additional clarification if needed, ensuring that all aspects of the feature are well-defined. The output is a structured PRD in Markdown format, which can be easily stored and referenced in project documentation. This format includes sections for feature names, goals, user personas, user stories, requirements, acceptance criteria, and more, allowing for a thorough understanding of the feature's purpose and implementation.
This skill is particularly beneficial for teams that need to align on product vision and execution, as it helps to avoid miscommunication and scope creep. By clearly outlining the problem being solved, the solution proposed, and the expected impact, teams can make informed decisions about feature development. The structured approach also aids in tracking progress and validating completion against defined acceptance criteria.
Overall, the Feature PRD Prompt skill is ideal for product managers, business analysts, and any team members involved in the product development lifecycle who need to create clear and actionable PRDs from high-level feature requests.
When to use it
Use this skill when you need to generate a PRD for a new feature based on an Epic, ensuring all necessary details are captured.
When not to use it
This skill may not be suitable for teams that prefer informal documentation or do not follow a structured PRD process.
What you can build with it
Creating a PRD for a New Feature
When starting a new feature development, use this skill to generate a comprehensive PRD that aligns the team on objectives and requirements.
Aligning Teams on Feature Scope
Utilize the skill to document the scope and acceptance criteria for a feature, helping to prevent scope creep during development.
Documenting User Stories and Personas
Employ this skill to clearly articulate user stories and target personas, ensuring that the development team understands the end-users' needs.
How to install Feature PRD Prompt
View source1. Install with the skills CLI
npx skills add github/awesome-copilot/breakdown-feature-prd --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by githubFeature 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]
Frequently asked questions about Feature PRD Prompt
Similar skills
Markdown to HTML Conversion
Efficiently convert Markdown documents to HTML.
Code Tour
Create structured walkthroughs for codebases.
Acquire Codebase Knowledge
Streamline onboarding with comprehensive codebase documentation.
Documentation & Modernization
Streamline codebase documentation and modernization planning.
Azure Resource Visualizer
Generate architecture diagrams for Azure resources.
CLAUDE.md Improver
Optimize your CLAUDE.md files for better project context.