Product requirements documents help teams understand what to build. This skill creates them using a file-based planning system. It keeps all your thinking in one place to avoid context switching.
The process uses four different files. One file holds raw notes and ideas. Another tracks your progress. The main file has the product requirements. The last file describes the technical design. This structure makes the work traceable and coherent.
Anyone making a PRD will benefit from this organized approach. It saves time and keeps everyone on the same page.
Global
mkdir -p ~/.claude/skills/prd-plannerProject
mkdir -p .claude/skills/prd-plannerSource 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