What problem does it solve? Writing a Product Requirements Document for a new product from scratch often produces inconsistent, incomplete documents that miss requirements, technical constraints, or properly sequenced epics and stories. This Skill provides a rigid, validated template structure so every greenfield PRD covers goals, requirements, UI vision, technical assumptions, epics, and handoff prompts. ## Core Features & Use Cases - Complete PRD Structure: Eight sections covering goals and background, functional and non-functional requirements, UI design goals, technical assumptions, epic list, epic details with stories and acceptance criteria, checklist results, and next-step handoff prompts. - Mandatory Elicitation Points: Interactive user validation at requirements, UI goals, technical assumptions, and epic sections, with pre-population from project briefs or technical-preferences files. - AI-Agent-Sized Stories: Enforces vertical-slice stories sized for 2-4 hour focused sessions, with sequential epic ordering where Epic 1 establishes foundation plus initial functionality. - Use Case: A product manager starting a new product invokes the new-product-prd workflow, which uses this template to produce a docs/prd.md with numbered FR/NFR requirements, an approved epic list, detailed stories with acceptance criteria, a pm-checklist validation report, and ready-to-use UX Expert and Architect prompts. ## Quick Start Ask the agent to create a PRD for a new product using the new-product-prd workflow, which applies this greenfield template section by section.