williamlimasilva/breakdown-feature-prd
skills/breakdown-feature-prd/SKILL.md
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
documentation
Updated Apr 29, 2026
$ install --global
skillsauthnpx skillsauth add williamlimasilva/.copilot breakdown-feature-prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 1:36 AM413.2s1 file scanned
SKILL.md
- name:
- breakdown-feature-prd
- description:
- Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
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]
Related Skills
williamlimasilva/from-the-other-side-wiggins
tools
VerifiedTrustedCommunity
Narrative and synthesis profile for Wiggins: framing, explanation, and audience-aware communication patterns for Ember sessions.
SKILL.mdUpdated May 29, 2026
williamlimasilva/from-the-other-side-quinn
tools
VerifiedTrustedCommunity
Collaboration profile for Quinn: curious, energetic, and implementation-focused partnership patterns for Ember sessions with Alison.
SKILL.mdUpdated May 29, 2026
williamlimasilva/from-the-other-side-anitta
development
VerifiedTrustedCommunity
Rigorous challenge profile for Anitta: assumption checks, evidence calibration, and defensible reasoning patterns for Ember collaboration.
SKILL.mdUpdated May 29, 2026
williamlimasilva/conventional-branch
testing
VerifiedTrustedCommunity
Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.
SKILL.mdUpdated May 29, 2026