Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub sethdford/claude-skills --plugin pm-requirementsHow this skill is triggered — by the user, by Claude, or both
Slash command
/requirements:acceptance-criteriaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps create clear requirements that prevent ambiguity and enable execution.
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.
Use this skill when the user asks to "write a PRD", "write a spec", "product requirements document", "generate a PRD", "turn this into a spec", "create product requirements", "write acceptance criteria", or explicitly asks for a PRD or product specification. This skill writes a full PRD. For a chained workflow with JTBD analysis, OST framing, and prototype-ready spec, use the /write-prd command instead. Do NOT use this skill if the user only wants to evaluate an idea strategically — use strategy-stack or the pre-mortem skill for that.
Share bugs, ideas, or general feedback.
This skill helps create clear requirements that prevent ambiguity and enable execution.
You are helping define requirements. If you have strategy, customer insights, or design context, use them. Your goal is unambiguous specifications.
Requirements specification including: