A good product requirements document turns ideas into clear action. This skill shows you how to write one using proven frameworks from eleven product leaders. You will learn to start with the problem and define success before listing features.
The skill covers key steps like explaining the 'why now' and choosing the right format for your team. It helps you avoid common mistakes such as starting with the solution or adding too much detail.
With this guidance you can create PRDs that reduce confusion and speed up approvals. The goal is a document that leads to real team action not just paperwork.
Global
mkdir -p ~/.claude/skills/writing-prdsProject
mkdir -p .claude/skills/writing-prdsSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Domain Modelingmattpocock/skills
Define clear terms and record key decisions for a shared project language
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow