Structured PRD generation prompt for breaking down Epics into detailed feature specifications.
Works with
Generates complete Product Requirements Documents in markdown format with standardized sections covering goals, user personas, stories, functional and non-functional requirements, and acceptance criteria
Prompts for clarifying questions when insufficient information is provided, ensuring comprehensive feature definition before engineering handoff
Organizes output into a consistent file stru
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbreakdown-feature-prdExecute the skills CLI command in your project's root directory to begin installation:
Fetches breakdown-feature-prd from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate breakdown-feature-prd. Access via /breakdown-feature-prd in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
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.
The output should be a complete PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.
<user persona>, I want to <perform an action> so that I can <achieve a benefit>."Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
mattpocock/skills
mattpocock/skills
parcadei/continuous-claude-v3
We added breakdown-feature-prd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
breakdown-feature-prd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
breakdown-feature-prd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
breakdown-feature-prd reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for breakdown-feature-prd matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for breakdown-feature-prd matched our evaluation — installs cleanly and behaves as described in the markdown.
breakdown-feature-prd reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for breakdown-feature-prd matched our evaluation — installs cleanly and behaves as described in the markdown.
breakdown-feature-prd reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: breakdown-feature-prd is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 29