From PRD-Driven Context Engineering
Generates structured product requirements documents (PRDs) with defined fields, evidence validation, and quality gates. Useful for product planning and specification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-ce:SKILL_TEMPLATEThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
[One sentence summary of the skill's purpose.]
[One sentence summary of the skill's purpose.]
[Define the primary output structure this skill produces]
| Element | Definition | Evidence |
|---|---|---|
| Field 1 | What this captures | How to validate |
| Field 2 | What this captures | How to validate |
See assets/output-template.md for copy-paste template.
[Detailed instructions for this step]
[Detailed instructions for this step]
[Detailed instructions for this step]
How this is evaluated: This skill's output is scored by
scripts/readiness.py(a deterministic, $0, no-LLM proxy). Clearing a gate is permission to advance, not the goal — the goal is evidence. Padding inputs to move the score without moving the evidence is a frozen-replay defect. SeePRINCIPLES.mdP7.
| Pattern | Example | Fix |
|---|---|---|
| Bad pattern 1 | "Example" | → "Better approach" |
| Bad pattern 2 | "Example" | → "Better approach" |
| Evidence fabrication | Back-filling confidence/evidence to clear a gate | → Cite a real source or mark the gap; never invent to pass (P4 anti-leakage, P7) |
references/[file].md — [Description of when to use]assets/[template].md — [Description of template purpose][What happens after this skill completes? What stage/skill comes next?]
npx claudepluginhub mattgierhart/prd-driven-context-engineering --plugin prd-ceGenerates a structured Product Requirements Document from a feature description, validated with the user before saving.
Guides interactive creation of Product Requirements Documents (PRDs) through structured questions across 15 sections like executive summary and problem statement. Saves as Markdown file.
Activate for: PRD, product requirements document, product requirements, full requirements, initiative doc, initiative requirements, platform change, new product, product launch, major release, quarterly initiative, program brief, product vision doc, comprehensive requirements, cross-functional alignment doc, launch plan requirements, multi-team initiative. NOT for: single-feature specifications (use official /write-spec), roadmap planning (use official /roadmap-update), sprint planning (use official /sprint-planning).