Individual skill
writing-prds
Help users transform abstract ideas into actionable project specs that align engineering and design teams on the problem and success metrics.
skills/writing-prds/SKILL.md
Source commit 13598cc54e09399bc1bc1398b0fca284110efb2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,475
- Repository last updated
- Jul 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-assistant Repository topic
- claude Repository topic
- claude-code Repository topic
- lenny-rachitsky Repository topic
- llm Repository topic
- pm-tools Repository topic
- product-management Repository topic
- skills Repository topic
- product-skills Repository topic
- engineering Derived category
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,019 bytesreferences/artifacts.mddoc · 40,484 bytesreferences/guest-insights.mddoc · 26,123 bytes
Read excerpt
# Writing Product Requirement Documents
Define clear problems and bounded solutions to maximize team velocity and creative output.
Help the user with writing product requirement documents using insights from 14 guests and posts across Lenny's Podcast and Newsletter.
## How to Help
1. **Drafting the core problem** - Assist in articulating a concise problem statement that is agnostic of any specific solution.
2. **Establishing success metrics** - Help define specific, measurable outcomes that will act as a filter for future feature requests.
3. **Defining project boundaries** - Guide the user through narrowing fuzzy requests into a bounded concept using shaping techniques.
4. **Reviewing for clarity** - Audit existing drafts for brevity, readability, and technical awareness to prevent micromanagement.
## Core Principles