This prompt helps you create a detailed Product Requirements Document or PRD. It takes a high-level feature idea from an Epic and breaks it down into a clear plan. Product managers and engineering teams use this to stay on the same page.
The PRD becomes the single source of truth for building the feature. It includes user stories, requirements, and acceptance criteria. This saves time and reduces confusion during development.
Anyone involved in planning software features can benefit. It turns vague requests into actionable specifications that teams can follow step by step.
Global
mkdir -p ~/.claude/skills/breakdown-feature-prdProject
mkdir -p .claude/skills/breakdown-feature-prdSource 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