Turn a feature idea into a clear PRD — problem, users, requirements, and success metrics.
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./apps/desktop/electron/default-skills/prd-writer/SKILL.mdWrite the spec that gets a team building the right thing. A good PRD isn't a feature list — it's a shared understanding of the problem, who has it, what "done" means, and how you'll know it worked. It closes the gaps where projects usually go sideways.
Use Product Spec to turn a feature idea, request, or rough notes into a product requirements document (PRD) or one-pager. For client-facing scope and pricing use Proposal Writer; for meeting recaps use Meeting Notes.
A structured doc: Summary, Problem, Users & Context, Goals / Non-goals, Requirements (prioritized), Success Metrics, Risks & Open Questions. Keep it as short as the problem allows.
4684714
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.