Craft detailed PRDs translating business goals into feature-level requirements.
npx skills add https://github.com/Yukine5377/common --skill po-prd
Please help me install this Agent Skill. Skill: po-prd Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/po-prd Command: npx skills add https://github.com/Yukine5377/common --skill po-prd
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.
Draft a PRD using BRD approval, user research insights, and design guidelines to align business goals with technical feasibility.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document (PRD), translate business goals into feature-level requirements by incorporating BRD approvals, user research, and design guidelines to inform UI/UX, development, and QA teams.
A PRD for sprint planning should include a problem statement, goals, success metrics, functional and non-functional requirements, user stories with acceptance criteria, prioritization, UI/UX requirements, and open questions.
Structure user stories and acceptance criteria by expressing each functional requirement as a user story with explicit acceptance criteria and prioritization levels from P0 to P3 to ensure a complete, production-ready document.
Yes, this PRD framework aligns stakeholders with technical feasibility by documenting constraints, assumptions, dependencies, and out-of-scope items to bridge business value and tech team implementation.
The best way to define non-functional requirements and success metrics in a PRD is to explicitly document them alongside analytics tracking, localization needs, and target audience personas to measure feature impact.
You need BRD approval before drafting a PRD when translating high-level business goals into concrete feature requirements, ensuring the product owner has validated business value prior to technical scoping.
vladm3105Create Layer 1 BRD artifacts defining business needs and strategic objectives.
tiagofurDecompose features into prioritized tasks with acceptance criteria and estimates.
FelipeMainesGenerate and validate Scrum user stories from PRD context.
whimzyLiveDecompose large user stories into smaller stories using eight systematic splitting patterns.
