How do I install the Breakdown Feature Prd skill?

Run npx skillmds@latest add vbrevik/breakdown-feature-prd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Breakdown Feature Prd safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Breakdown Feature Prd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Breakdown Feature Prd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Breakdown Feature Prd?

vbrevik (@vbrevik) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Breakdown Feature Prd by vbrevik — Agent Skill

Name: Breakdown Feature Prd
Rating: 4.2 (5 reviews)
Author: vbrevik

File contents

Feature PRD Breakdown

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]

---name: breakdown-feature-prddescription: Use after creating a PRD to decompose individual features into detailed mini-PRDs with epic linking, functional/non-functional requirements, and per-feature acceptance criteria.---# Feature PRD BreakdownAct 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 FormatThe 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]

Frequently asked questions

Breakdown Feature Prd