skilld
All skills
github avatar

/breakdown-feature-prd

@90921cc official
by githubgithub/awesome-copilot40k stars
5,040

Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/breakdown-feature-prd

This session only. Nothing lands on disk.

SKILL.md

≈29 tokens always: the name and description. ≈583 when used: this file.

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]

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is a prompt template for generating Product Requirements Documents (PRDs). It defines a standard workflow for documentation and does not contain malicious code, sensitive data access, or network operations.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    1/1 file flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 90921cc. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 16 hours ago.

Activeupdated 5 months ago

Topics

  • Documentation
  • prd
  • product-management
  • requirements
  • feature-planning
  • saas
  • epic
  • user-stories
  • acceptance-criteria

README badge

README badge for github/awesome-copilot/breakdown-feature-prd

What it does

This skill prompts Claude to generate detailed Product Requirements Documents for new features based on an Epic, outputting structured Markdown with problem statement, user personas, stories, functional and non-functional requirements, and acceptance criteria. It targets product teams using Claude to formalize feature planning before handing off to engineering.

Generated from the current SKILL.md.

Frequently asked

What format does the PRD output need to be in?
The PRD is generated as Markdown and saved to `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.
Do I need to provide all the information upfront, or will the skill ask clarifying questions?
The skill will ask clarifying questions if you don't have enough information to ensure all aspects of the feature are well-defined.
What are the main sections included in the generated PRD?
The PRD includes Feature Name, Epic, Goal (Problem/Solution/Impact), User Personas, User Stories, Requirements (Functional and Non-Functional), Acceptance Criteria, and Out of Scope sections.

Generated from the current SKILL.md. These answers refresh after source changes.