Index of every page on this site: llms.txt
All skills
github avatar

/breakdown-feature-prd

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

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

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈117 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    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.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub yesterday.

Activeupdated 7 months ago
  • Documentation
  • prd
  • product-management
  • requirements
  • feature-planning
  • saas
  • epic
  • user-stories
  • acceptance-criteria

README badge

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

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.

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.