Skill

Official

Review

Audit score 70

breakdown-feature-prd

github/awesome-copilot

Generate detailed Product Requirements Documents for new features based on an Epic.

What is breakdown-feature-prd?

This skill prompts an AI agent to act as an expert Product Manager and create comprehensive PRDs for new features. Use it when you need to break down an Epic into well-defined feature requirements with user stories, acceptance criteria, and functional/non-functional specifications.

Creates structured PRDs in Markdown with feature name, goals, user personas, and user stories
Defines functional and non-functional requirements with specific, unambiguous details
Generates acceptance criteria in checklist or Given/When/Then format for validation
Identifies out-of-scope items to prevent scope creep
Asks clarifying questions when information is incomplete
Saves output to organized directory structure under /docs/ways-of-work/plan/

How to install breakdown-feature-prd

npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-prd

Claude Code

Cursor

Windsurf

Cline

How to use breakdown-feature-prd

1.Provide the parent Epic details and a high-level description of the feature request
2.Optionally specify target users or initial feature ideas
3.The skill will ask clarifying questions if needed to fully understand the feature
4.Review the generated PRD in Markdown format at the specified output path
5.Use the PRD as the source of truth for engineering implementation and acceptance testing

Use cases

Good for

Breaking down a large Epic into a single feature PRD with complete requirements
Documenting user stories and acceptance criteria before engineering begins implementation
Creating a single source of truth for feature specifications across product and engineering teams
Defining non-functional requirements like performance, security, and accessibility upfront
Establishing clear scope boundaries and out-of-scope items for a feature

Who it's for

Product Managers creating feature specifications
Engineering teams needing detailed requirements before development
Technical leads planning feature implementation
Teams using Epic-driven product planning

breakdown-feature-prd FAQ

What information do I need to provide to use this skill?

At minimum, provide a link to the parent Epic and a high-level description of the feature. Optionally include target users or initial feature ideas. The skill will ask clarifying questions if more details are needed.

Where is the PRD output saved?

The PRD is saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md in Markdown format.

Does this skill generate acceptance criteria?

Yes. For each user story or major requirement, it generates acceptance criteria in a clear format (checklist or Given/When/Then) that can be used to validate feature completion.

Can this skill help prevent scope creep?

Yes. The PRD includes an explicit 'Out of Scope' section that clearly lists what is not included in the feature, helping teams stay focused on defined requirements.

What if I don't have all the details about the feature yet?

The skill is designed to ask clarifying questions when information is incomplete, helping you flesh out all aspects of the feature before engineering begins.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.

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]

Surgical code refactoring to improve maintainability without changing behavior.

19k installsAudited