Write a one-page PRD engineers love

Steps

1. 1Lead with problem statement and target user's current workaround
2. 2Define success metrics with baseline numbers and targets
3. 3List in-scope v1 and explicitly out-of-scope items
4. 4Specify edge cases and non-functional requirements (perf, a11y, privacy)
5. 5Keep an open-questions section with owners and due dates
6. 6Review with engineering before finalizing; incorporate feasibility push-back

Common Pitfalls

• ▲Solution mockups posing as requirements
• ▲Success metrics undefined until post-launch retro

Commands

$ npx skills add aniruddhaadak80/skills --skill specs-launch-prd-one-page

$ npx skills add aniruddhaadak80/skills --skill specs-launch-prd-one-page -g

Tags