breakdown-feature-prd

Generate structured Markdown PRDs from epics and feature descriptions.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-feature-prd-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-feature-prd
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/breakdown-feature-prd
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-feature-prd-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts high-level epics and brief feature requests into a single, structured Product Requirements Document (PRD) that engineering and product teams can use as the source of truth, reducing ambiguity and back-and-forth during planning and implementation.

Core Features & Use Cases

  • Structured PRD Generation: Produces a complete Markdown PRD including feature name, links to Epic, goal (problem/solution/impact), user personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope items.
  • Clarification and Validation: Prompts for missing information and refines requirements through follow-up questions to ensure readiness for engineering handoff.
  • Use Case: A product manager provides an Epic and a short feature description and receives a ready-to-use PRD saved into the repository path for documentation and planning.

Quick Start

Use this prompt to generate a complete PRD from an epic and feature description, asking clarifying questions if information is missing.

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 epics into detailed product requirements documents for engineering handoff?

To convert epics into detailed product requirements documents, provide the epic and feature description to generate a structured Markdown PRD. This document includes goals, personas, user stories, requirements, and acceptance criteria for engineering handoff.

What is the best way to structure user stories and acceptance criteria from a brief feature request?

Structuring user stories and acceptance criteria from a feature request is best handled by generating a complete PRD. The PRD organizes the brief request into structured sections including functional requirements, non-functional requirements, and out-of-scope items.

Can I generate a PRD if my feature description is missing information?

Yes, you can generate a PRD with missing information because the process includes clarification and validation. It will prompt you with follow-up questions to gather missing details and refine requirements to ensure readiness for engineering handoff.

Does PRD generation work for SaaS product planning scenarios?

PRD generation does work for SaaS product planning scenarios, applying directly to convert epics into structured documents. It produces a complete Markdown file suitable for traceable storage and engineering handoff within SaaS environments.

How do I save a generated PRD to a specific repository path?

To save a generated PRD to a specific repository path, the output Markdown includes links to Epic docs and saves directly to your specified location. This ensures the document is stored traceably for documentation and planning purposes.