skills.rest
ripabak
ripabakCOMMUNITY
Explore all skills by this author →
GitHub

breakdown-feature-prd

Generate structured PRD documents from Epic summaries for engineering teams.

Updated Apr 25, 2026
Search Tags:#planning#specification#requirements#prd#epic#product-management#user-stories
One-click install
npx skills add https://github.com/ripabak/elysia-multi-tenancy-template --skill breakdown-feature-prd-ripabak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-feature-prd
Source: https://github.com/ripabak/elysia-multi-tenancy-template/tree/main/.agents/skills/breakdown-feature-prd
Command: npx skills add https://github.com/ripabak/elysia-multi-tenancy-template --skill breakdown-feature-prd-ripabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, shareable Product Requirements Documents (PRDs) from Epic inputs to align product, engineering, design, and QA, reducing ambiguity and rework across feature development.

Core Features & Use Cases

  • Automated PRD generation from an Epic summary, including sections for goal, user personas, user stories, acceptance criteria, functional and non-functional requirements, and scope.
  • Linkable references to the parent Epic PRD and architecture documents to ensure traceability and alignment.
  • Output ready-to-publish PRD docs that can be saved under docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md for team-wide access and versioning.

Quick Start

Paste the Epic summary and constraints to generate a complete, review-ready PRD.

Frequently Asked Questions about breakdown-feature-prd

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

FAQPage Schema
How do I convert an Epic into a PRD with user stories and acceptance criteria?▼

To convert an Epic into a PRD, paste the Epic summary and constraints to automatically generate a structured document containing user stories, acceptance criteria, and functional requirements for engineering alignment.

What sections should be included in a SaaS feature PRD?▼

A SaaS feature PRD should include Feature Name, Epic, Goal, User Personas, User Stories, functional and non-functional Requirements, Acceptance Criteria, and Out of Scope sections to guide engineering teams effectively.

How do I generate non-functional requirements from an Epic summary?▼

You can generate non-functional requirements by inputting the Epic summary into the PRD workflow, which automatically extracts constraints and structures them alongside functional requirements and acceptance criteria.

Can I link generated feature PRDs back to the parent Epic PRD?▼

Yes, generated feature PRDs include linkable references to the parent Epic PRD and architecture documents, ensuring full traceability and alignment across multiple product development squads.

What is the best way to structure PRD documents for multiple squads?▼

The best way to structure PRDs for multiple squads is saving them as prd.md files within docs/ways-of-work/plan/{epic-name}/{feature-name}/ directories for team-wide access and versioning.

Does PRD generation work without defining scope and risk considerations?▼

PRD generation explicitly handles scope and risk considerations by outlining Out of Scope sections and risk factors, ensuring engineering teams understand boundaries before development begins.

Related Skills

Explore More Product & Management Skills→
aigars-stgaigars-stg

prd

Generate, access, and validate Product Requirements Documents for feature development.

Community
Intermediate
X-School-AcademyX-School-Academy
19

dev-swarm-stage-sprints

Plan agile sprints by breaking product requirements into backlogs with acceptance criteria and test plans.

Official
Advanced
JochenYangJochenYang
21

product-manager

Generate structured PRDs and user stories with acceptance criteria.

Community
Intermediate
russosalvrussosalv
5

requirements-ingest

Convert unstructured stakeholder documents into structured Markdown requirement files.

Community
Advanced