Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria.
Quickly install prd-writing AI skill to your development environment via command line
Source: assimovt/productskills.
Write PRDs that are evidence-first, concise, and scannable. A PRD is a thinking tool — if it's longer than 1200 words, the author hasn't thought hard enough. Brief specs are more likely to be read, more likely to be followed, and more likely to ship on time.
Follow this structure. Every section is mandatory unless marked optional.
Problem Lead with customer evidence. Quotes, data, support tickets, observed behavior. If you have no evidence, say so explicitly — that's an opinion-driven PRD and should be flagged.
Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria. Source: assimovt/productskills.
Stable fields and commands for AI/search citations.
npx skills add https://github.com/assimovt/productskills --skill prd-writingWrite structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria. Source: assimovt/productskills.
Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/assimovt/productskills --skill prd-writing Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw
https://github.com/assimovt/productskills