breakdown-feature-prd

Structured PRD generation prompt for breaking down Epics into detailed feature specifications.

- Generates complete Product Requirements Documents in markdown format with standardized sections covering goals, user personas, stories, functional and non-functional requirements, and acceptance criteria

- Prompts for clarifying questions when insufficient information is provided, ensuring comprehensive feature definition before engineering handoff

- Organizes output into a consistent file structure (/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md) for centralized documentation management

- Includes explicit out-of-scope definition to prevent scope creep and establish clear feature boundaries

Feature PRD Prompt

Goal

Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.

Review the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.

Output Format

The output should be a complete PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.

PRD Structure

1. Feature Name

- A clear, concise, and descriptive name for the feature.

2. Epic