breakdown-feature-prd

Generates structured Product Requirements Documents from Epic-level feature requests.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-feature-prd-ultraviollettnympho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-feature-prd
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/breakdown-feature-prd
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-feature-prd-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often struggle to translate high-level Epic ideas into detailed, engineering-ready documentation. This Skill turns a feature request and its parent Epic into a complete Product Requirements Document that serves as the single source of truth for engineering teams. ## Core Features & Use Cases - Structured PRD Generation: Produces a full PRD covering goals, user personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope items. - Standardized Output Location: Saves the PRD as Markdown to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md for consistent documentation organization. - Clarifying Questions: Prompts for missing context when the feature request or Epic lacks sufficient detail. - Use Case: A product manager receives an Epic for a new notifications system and needs a PRD for the email-digest feature; this Skill generates the complete document with user stories and Given/When/Then acceptance criteria. ## Quick Start Ask the AI to create a feature PRD from your Epic by providing the Epic link and a high-level description of the feature idea.

Frequently Asked Questions about breakdown-feature-prd

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

FAQPage Schema
How do I create a PRD from an Epic?▼

Provide the parent Epic link and a high-level feature description, and the Skill generates a complete PRD with goals, personas, user stories, requirements, and acceptance criteria. If information is missing, it asks clarifying questions before writing.

What sections should a feature PRD include?▼

This PRD structure includes feature name, Epic links, goal with problem and solution, user personas, user stories, functional and non-functional requirements, acceptance criteria, and an out-of-scope section to prevent scope creep.

Where is the generated PRD file saved?▼

The PRD is saved as Markdown to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md, keeping documentation organized hierarchically by Epic and feature.

What format are the acceptance criteria written in?▼

Acceptance criteria are written per user story or major requirement using a checklist or Given/When/Then format, making them directly usable for validating feature completeness during development and testing.

What happens if my feature request lacks detail?▼

The Skill asks clarifying questions to fill gaps before generating the PRD, ensuring the final document is well-defined enough to serve as the single source of truth for engineering.