writing-prds
Installation
SKILL.md
Writing PRDs
Scope
Covers
- Turning a product idea into a decision-ready PRD with unambiguous scope, requirements, and success metrics
- Optionally producing a PR/FAQ (press release + FAQ) to force customer-centric narrative first
- For AI features: adding a Prompt Set + Eval Spec so “requirements” are testable and continuously checkable
When to use
- “Write a PRD / product spec / requirements doc for this feature.”
- “Turn these messy notes into a PRD we can align on.”
- “Create a PR/FAQ and then a PRD.”
- “This is an AI feature; I need evals + prompts to define behavior.”
When NOT to use
- You’re still choosing what strategy/market to pursue (do product vision / strategy first)
- You need discovery from scratch (research plan, problem validation) more than requirements -> use
problem-definition - You need a detailed engineering design doc (APIs, schemas, low-level architecture)
Related skills
More from liqiongyu/lenny_skills_plus
problem-definition
Define a product problem: problem statement, JTBD, alternatives, evidence, metrics. See also: writing-prds (solution spec).
13giving-presentations
Plan and deliver presentations: brief, narrative, slide outline, Q&A bank, rehearsal plan. See also: written-communication (async writing).
13competitive-analysis
Produce a Competitive Analysis Pack (alternatives map, landscape, battlecards, monitoring plan).
11pricing-strategy
Create a Pricing Strategy Pack (value metric, packaging, price points, conversion mechanics, rollout).
11startup-ideation
Generate and evaluate startup ideas: theses table, scorecard, top idea brief, validation plan. See also: startup-pivoting (existing product).
11writing-north-star-metrics
Define or refresh a product North Star metric + driver tree.
11