mcpField
B
breakdown-feature-prd

breakdown-feature-prd

github.com/githubDevelopment40.5k10.0k installsUpdated today
Repository

About breakdown-feature-prd

A product-management skill that turns a feature idea and its parent Epic into a detailed PRD in Markdown. It prompts for clarification when context is missing and structures requirements, user stories, and acceptance criteria for engineering teams.

Key features

  1. 01Structure a detailed feature PRD
  2. 02Connect the feature to its Epic
  3. 03Define personas and user stories
  4. 04Specify functional and quality requirements
  5. 05Write acceptance criteria and scope

Use cases

  1. 01Turn an Epic feature into a PRD
  2. 02Clarify incomplete feature requests
  3. 03Prepare requirements for engineering review

Install

Copy the command and run it in a terminal.

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

After installing, type/breakdown-feature-prdin Claude Code to confirm it loaded.

Details

From the project README

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]

Comments

Markdown supported