Breakdown Feature Prd
GitHubOfficialOriginally contributed by @craigbekker as prompts/breakdown-feature-prd.prompt.md; moved into a skill by pull request #761Distributed by GitHub
- Skill
- Content generator
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill acts as an expert Product Manager to transform high-level feature ideas and Epic context into structured, comprehensive Product Requirements Documents. It ensures that engineering teams have a clear, single source of truth by defining the problem, solution, user stories, functional requirements, and acceptance criteria for new features.
What it does
- Translates high-level feature requests into formal PRD documentation.
- Structures requirements into functional and non-functional categories.
- Defines user personas and specific user stories for the feature.
- Establishes clear acceptance criteria using Given/When/Then or checklist formats.
- Identifies out-of-scope items to prevent project scope creep.
- Prompts for clarifying information if the initial feature request is incomplete.
When to use it
- When you need to turn a high-level feature idea into actionable engineering requirements.
- When preparing documentation for a new feature within an existing Epic.
- When you need to align stakeholders on the goals, impact, and constraints of a feature.
- When you need to establish clear acceptance criteria for development and QA teams.
Advantages
- Ensures consistency in documentation across different features.
- Reduces ambiguity for engineering and design teams.
- Helps identify edge cases and out-of-scope items early in the process.
- Provides a structured framework that covers both functional and non-functional requirements.
Usage examples
- “Create a PRD for a new 'Dark Mode' toggle feature under the 'UI Refresh' Epic.”
- The agent will generate a structured PRD including the problem statement, user stories for toggling themes, functional requirements for state persistence, and acceptance criteria.
- “I have an Epic for 'User Onboarding'. Create a PRD for a new 'Email Verification' feature.”
- The agent will produce a document outlining the verification flow, security requirements, and user stories for the email confirmation process.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/breakdown-feature-prd/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip breakdown-feature-prd.zip -d .agents/skills
Documentation by craigbekker
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]
Files
- ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.4 KiB
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Originally contributed by
@craigbekkeras prompts/breakdown-feature-prd.prompt.mdmoved into a skill by pull request #761
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/breakdown-feature-prd · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- craigbekker
AutoGineer is not affiliated with or endorsed by craigbekker or GitHub.
Related skills
Marketing Plan
Corey Haines· Community
Generates a comprehensive, executable 12-month marketing plan structured by the AARRR framework for fractional CMOs and founders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskGitHub stars of the source repository59k
Revops
Corey Haines· Community
Expert guidance for designing and optimizing revenue operations, lead lifecycle management, and marketing-to-sales handoff processes.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Ab Testing
Corey Haines· Community
A comprehensive framework for planning, executing, and analyzing statistically rigorous A/B tests and growth experimentation programs.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Pricing
Corey Haines· Community
Expert guidance on SaaS pricing strategy, packaging, monetization, and auditing pricing pages for human and AI-agent readability.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Community Marketing
Corey Haines· Community
A strategic framework for building and managing online communities to drive product growth, brand loyalty, and user engagement.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Paywalls
Corey Haines· Community
Expert guidance for designing and optimizing in-app upgrade flows, paywalls, and feature gates to maximize conversion.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download breakdown-feature-prd.zip