writing-prds

Installation
Summary

Help teams write focused, actionable product requirements documents using frameworks from 11 product leaders.

  • Start with problem and context before solutions; include "why now" to justify timing and urgency against competing priorities
  • Choose the right format for your product type: traditional PRDs for feature specs, prototypes or prompt sets for AI features, executable evals as living requirements
  • Define success upfront with clear metrics and outcomes; keep documents lightweight and outcome-focused rather than exhaustively detailed
  • Use PR/FAQ format to describe customer, problem, and solution in factual language; consider AI scaffolding for basics like user stories and out-of-scope items
SKILL.md

Writing PRDs

Help the user write effective product requirements documents using frameworks and insights from 11 product leaders.

How to Help

When the user asks for help with PRDs:

  1. Start with the why - Ask about the problem being solved and why it matters now, before features
  2. Define success upfront - Help them articulate how they'll know the feature succeeded
  3. Choose the right format - Discuss whether they need a traditional doc, a prototype, or executable evals
  4. Keep it actionable - Ensure the document leads to clear team action, not just documentation

Core Principles

Lead with problem and context

Maggie Crowley: "The most important section is the first part - what is the background and context? What is the problem, why does it matter, and why does it matter now?" Center the team on the 'why' and the urgency before discussing solutions.

The PR/FAQ forces clarity

Related skills
Installs
1.7K
GitHub Stars
879
First Seen
Jan 29, 2026