PlugWiki

breakdown-feature-prd Skill (awesome-copilot) for Claude: What It Does and How to Install It

Makes Claude write a product requirements document for one feature, based on its parent Epic.

Installs
10K
on skills.sh
Stars
40.7K
on GitHub
Updated
Oct 2026
last repo commit

Give Claude a feature idea and the parent Epic. It acts as a product manager for a large SaaS platform and writes a PRD with eight sections: feature name, Epic link, goal, user personas, user stories, requirements, acceptance criteria and out of scope. If information is missing, SKILL.md tells it to ask clarifying questions.

The PRD is saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md in your project. The skill is one file with no scripts. It is part of the awesome-copilot collection from GitHub, which describes its customizations as sourced from third-party developers.

Good for

  • Product managers turning an Epic into a feature spec
  • Engineers who need clear requirements before building
  • Teams that keep planning docs in the repo
  • Anyone writing user stories and acceptance criteria

Install breakdown-feature-prd

Claude Code

  1. 1

    Copy this prompt.

    Install the breakdown-feature-prd skill in Claude Code. Run this command:
    
    npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-prd
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

The plugin route above is for Copilot CLI. For Claude Code, use the skills-only routes, which install just this skill.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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

Sections in SKILL.md

  1. Goal
  2. Output Format
  3. PRD Structure
  4. Context Template

Key facts

License
MIT
Installs on skills.sh
10,039 (Nov 2, 2026)
Last repo commit
Oct 30, 2026

What it includes

  • Acts as a product manager and asks if info is missing

    Reviews your feature request and the parent Epic, then writes a PRD. SKILL.md says to ask clarifying questions if it lacks information.

    Try: “Write a PRD for a saved-search feature. The Epic is in docs/epics/search/epic.md.”

    Read · Goal and clarifying questions

  • Eight sections from name to out of scope

    Feature name, Epic, Goal (problem, solution, impact), User Personas, User Stories, Requirements, Acceptance Criteria and Out of Scope.

    Write · PRD structure

  • "As a persona, I want to action so that benefit"

    Covers primary paths and edge cases in that sentence form.

    Write · User stories

  • Functional and non-functional lists

    Functional requirements say what the system must do. Non-functional ones cover performance, security, accessibility and data privacy.

    Write · Requirements

  • Checklist or Given/When/Then per story

    Used to check the feature is complete and correct.

    Write · Acceptance criteria

  • Writes prd.md under /docs/ways-of-work/plan

    Saves to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.

    Write · Save the PRD

From the official docs

Permissions

Low risk

The skill writes one PRD file into your repo. The Copilot CLI plugin route also installs agents that can run terminal commands and create GitHub issues, so use the skills-only route if you only want this skill.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • The plugin route adds agents with more power

    The project-planning plugin installs 7 agents. Their tool lists include running terminal commands (implementation-plan, research-technical-spike, task-planner) and creating or updating GitHub issues (prd). Use the skills-only install if you want just this skill. github.com

  • It writes a file under /docs

    SKILL.md saves the PRD to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md. Check the path before you commit it. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only mode. Decline the file write if you only want the PRD text in chat.
Sign-in and keysSKILL.md names no account or key.
Scopes
  • Writes prd.md under /docs/ways-of-work/plan/ in your project

Questions

What does the breakdown-feature-prd skill do?

It makes Claude write a PRD for one feature. Claude uses the parent Epic and your feature idea, and saves a Markdown file with goal, personas, stories, requirements, acceptance criteria and scope.

How do I install it?

Use the install box at the top of this page. For Copilot CLI there is a plugin route. For Claude Code, Codex and others, the box lists skills-only commands.

Where does it save the PRD?

SKILL.md says /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md. Check that this path suits your repo.

What is the project-planning plugin?

It is a Copilot CLI plugin in awesome-copilot with 8 skills and 7 agents for planning. This skill is one of the 8. Some of its agents can run terminal commands or create GitHub issues, so read them first.

Do I need an Epic first?

The skill expects a parent Epic and links it in the PRD. The sibling breakdown-epic-pm skill in the same plugin writes an Epic PRD.

Does it need an API key?

SKILL.md names no key and the skill is one file with no scripts.

Is it safe?

The skill is one text file with no scripts. It writes one Markdown file in your repo at the path above. The plugin route adds agents that can run terminal commands or create GitHub issues, so skip it if you only want this skill.

Information

updated Nov 2, 2026

Folder
skills/breakdown-feature-prd

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3
  1. breakdown-feature-prd SKILL.md · github.com
  2. project-planning plugin.json · github.com
  3. project-planning plugin README · github.com

Updated Nov 2, 2026.