breakdown-feature-prd
From the author
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
Install
npx skills add github/awesome-copilot --skill breakdown-feature-prd -a claude-code
Installs to .claude/skills/breakdown-feature-prd/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 95
Security100
Provenance95
Maintenance100
Licence100
Adoption71
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- breakdown-epic-pmgithub/awesome-copilotPrompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.Planning★ 40.3K
- prdgithub/awesome-copilotGenerate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.Planning★ 40.3K
- breakdown-epic-archgithub/awesome-copilotPrompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.Planning★ 40.3K
- breakdown-plangithub/awesome-copilotIssue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.Planning★ 40.3K
- write-specanthropics/knowledge-work-pluginsWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.OfficialWriting★ 31K
- pm-specnexu-io/open-designProduct spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".Planning★ 102.9K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in