Guide · Agent skill
How to use the Feature PRD Writer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Feature PRD Writer is an agent skill, a packaged set of instructions that tells an AI agent how to handle one kind of task. Once installed, it makes the agent act like a product manager when you ask for a feature spec: you give it a feature idea and its parent epic, and it drafts a Markdown Product Requirements Document (PRD). This guide explains what the skill does, how to install it, how to trigger it and what to check in the output before anyone relies on it.
Feature PRD Writergithub/awesome-copilot · MIT Download the skill Quick start
- 1Download the ZIP. Download the skill ZIP from this page and unzip it to get the breakdown-feature-prd folder containing SKILL.md.
- 2Place the folder. Move the folder into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill there instead.
- 4Describe the feature and epic. Ask for a feature PRD in plain language, including the feature idea, the parent epic and any target users.
- 5Answer clarifying questions. If the agent asks about users, metrics or scope, answer them so the PRD is specific rather than guessed.
- 6Review the Markdown PRD. Check metrics, personas, requirements and acceptance criteria against your own data before sharing with engineering.
What does the skill make the agent do?
The skill takes a high-level feature or enabler from an epic and produces a detailed PRD. The source describes the PRD as the single source of truth for the engineering team and as the input for a later technical specification.
The generated PRD follows a fixed structure: feature name, epic links, goal (problem, solution and impact), user personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope items. If key information is missing, the skill tells the agent to ask clarifying questions before writing the document.
- Feature name and link to the parent epic PRD and architecture documents
- Goal: problem, solution and expected impact
- User personas and user stories in the 'As a ... I want to ... so that I can ...' format
- Functional and non-functional requirements
- Acceptance criteria as a checklist or Given/When/Then
- Out-of-scope items to limit scope creep
How do you install the Feature PRD Writer skill?
Download the skill ZIP from this page and unzip it. The skill is a folder containing a single file, SKILL.md. Place the folder in one of these locations: ~/.claude/skills/ to make it available across your projects, or the .claude/skills/ folder inside a specific project to make it available only there.
If you use the Claude apps instead, you can upload the skill under Settings → Capabilities → Skills.
- Personal: unzip into ~/.claude/skills/
- Project only: unzip into the project's .claude/skills/ folder
- Claude apps: upload under Settings → Capabilities → Skills
How do you trigger the skill with a natural request?
You do not need a special command. Describe the feature and mention the epic in plain language, and the agent should use the skill when the request matches its purpose. Include the feature idea, the epic it belongs to, and any known target users, since these map onto the skill's context template.
The skill's context template has three fields: the epic documents, the feature idea and optional target users. Filling them in gives the agent more to work with and reduces the number of clarifying questions it asks.
- Feature idea: a short description of what the user wants
- Epic: a link or name for the parent epic documents
- Target users: optional first thoughts on who the feature is for
What does a good example request look like?
Here is an example of the kind of request the skill is built for. Adjust the feature and epic to match your own work. The output will be a Markdown PRD, saved according to the output path the skill specifies: /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.
Expect the agent to ask follow-up questions if the epic or the feature idea is vague, such as who the users are or what success looks like.
- Example: 'Write a PRD for a bulk CSV import feature under our Data Onboarding epic. Target users are account admins migrating from spreadsheets.'
- Example: 'Draft a feature PRD for in-app notification preferences, based on the Notifications epic.'
What should you check before using the PRD?
Treat the output as a first draft. The skill is a generic template, so it may not match your company's PRD standards, required sections or approval steps. Generated text can also include invented details about metrics or users, so check every number, persona and target against your own data and research.
Read the acceptance criteria closely, because they are meant to validate the finished feature. Remove or correct anything the epic does not support.
- Check metrics and impact claims against real data
- Confirm personas match your actual users
- Verify that out-of-scope items agree with the epic
- Adapt the structure to your internal approval process
Is it safe to run?
The skill is a prompt template only. According to the source, it does not run scripts and does not use the network. It does not connect to any service. Its only file is SKILL.md, and the source lists no required tools or accounts.
- Runs scripts: no
- Uses network: no
- Requires: nothing listed
- Licence: MIT
What people use it for
- Drafting a feature spec for a product manager from an existing epic
- Giving engineers a consistent PRD structure before they write a technical spec
- Teaching students how product requirements documents are organised
- Producing a first-draft list of user stories and Given/When/Then acceptance criteria to refine in review
Frequently asked questions
How do I install the breakdown-feature-prd skill?
Download the ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
Does the Feature PRD Writer skill need anything else installed?
The source lists no requirements. The skill is a single SKILL.md prompt file that does not run scripts and does not use the network.
Is the breakdown-feature-prd skill free to use?
The skill is published under the MIT licence, as stated on this page. The source does not mention pricing for any Claude plan, so check your own plan for access to skills.
Will the PRD be accurate enough to send straight to engineering?
Not without review. The output is generated text and can contain invented details about metrics or users. Check it against your data and your company's PRD process before sharing it.
Is this skill a good fit for a company with a strict PRD process?
Probably not as-is. The template is generic and may not match internal standards or required approvals, so you would need to adapt its structure to your process.
What should I do if the agent does not produce a PRD?
Make sure the skill folder is in one of the supported locations and that SKILL.md is inside it. Then give a clearer request that names the feature idea and the parent epic, since the skill is designed for requests based on an epic.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a product manager drafting feature specs from an existing epic, an engineering team wanting a consistent PRD structure, or a student learning how PRDs are organised. Pick something else if you need a validated, company-specific PRD process with required approvals, since this template is generic and its output needs careful review.
Download the skill