breakdown-feature-prd

Converts epics and feature ideas into structured feature-level PRD documents.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill breakdown-feature-prd-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-feature-prd
Source: https://github.com/jason23452/my-skill/tree/main/flow/breakdown-feature-prd
Command: npx skills add https://github.com/jason23452/my-skill --skill breakdown-feature-prd-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level epic or vague feature idea into an engineering-ready PRD is slow and error-prone, often leaving gaps in user stories, acceptance criteria, and scope that cause rework later. ## Core Features & Use Cases - Structured PRD Generation: Produces a complete feature PRD covering goals, personas, user stories, functional and non-functional requirements, Given/When/Then acceptance criteria, and out-of-scope items. - Gap-Driven Clarification: Diagnoses missing information (personas, entry points, triggers, edge cases) and asks targeted questions instead of guessing product facts. - ADO Batch Mode: Lists Azure DevOps User Story work items, expands selected stories into traceable PRDs, and supports batch draft and finalize workflows. - Use Case: A product manager selects three ADO user stories from an epic and receives three consistent, engineering-ready PRDs with acceptance criteria and open questions flagged as TBD. ## Quick Start Ask the assistant to break down your epic or feature idea into a feature-level PRD with user stories and acceptance criteria.

Frequently Asked Questions about breakdown-feature-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a feature PRD from an epic?▼

Provide the epic, feature idea, target users, core problem, and success metrics, and the skill expands them into a full PRD with goals, personas, user stories, requirements, and acceptance criteria. Missing information is flagged as TBD or asked as clarifying questions rather than guessed.

How to write acceptance criteria in Given When Then format?▼

Each acceptance criterion states a precondition (Given), a user or system action (When), and an observable result (Then). Success, failure, permission, empty-state, and boundary cases are split into separate testable criteria.

Can I generate PRDs from Azure DevOps user stories?▼

Yes, the batch mode lists current ADO User Story work items, lets you select multiple items, and expands each into a PRD preserving traceability to the source story id, URL, title, state, and acceptance criteria.

What happens when feature requirements are incomplete?▼

The skill asks targeted clarifying questions covering personas, entry points, triggers, success outcomes, scope, and edge cases instead of inventing product facts. Unresolved items are marked TBD and linked to specific PRD fields as open questions.

Where are the generated PRD files saved?▼

By default PRDs are written as Markdown to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md. If the project follows a different documentation convention, that convention is used and the actual path is reported.