po-prd

What problem does it solve?

PRD is a central document that translates business goals into concrete feature requirements for the tech team. This skill guides a Product Owner to describe features in detail, define acceptance criteria, and lay the groundwork for sprint planning, ensuring alignment between business value and technical feasibility.

Core Features & Use Cases

• Structured PRD framework: Document Header & Status, Problem Statement, Goals & Success Metrics, Target Audience & Personas, Assumptions & Constraints, Functional Requirements, User Flow, UI/UX Requirements, Analytics & Tracking, Non-functional Requirements, Localization, Dependencies, Out of Scope, Open Questions, and Revision History.
• Clear user stories and acceptance criteria: Each requirement is expressed as a user story with explicit acceptance criteria and prioritization (P0–P3).
• End-to-end guidance and templates: Provides templates and examples to speed up PRD creation and ensure consistency across features.
• Use cases include feature description, UI/UX guidance, and sprint-ready planning inputs.

Quick Start

Draft a PRD using BRD approval, user research insights, and design guidelines to align business goals with technical feasibility.