Generate a structured PRD JSON file from a problem description.
npx skills add https://github.com/finleysg/bhmc-admin --skill write-a-prd
Please help me install this Agent Skill. Skill: write-a-prd Source: https://github.com/finleysg/bhmc-admin/tree/main/.claude/skills/write-a-prd Command: npx skills add https://github.com/finleysg/bhmc-admin --skill write-a-prd
This skill helps product teams turn vague feature ideas into a detailed PRD, reducing ambiguity and misalignment across stakeholders. It guides you through problem framing, scope definition, success criteria, milestones, risks, and validation plans so everyone shares a single vision.
Create a PRD for a feature by providing a detailed problem statement, scope, goals, and acceptance criteria. The skill will generate a PRD JSON and place it in the /plans directory.
High-intent search queries and answers about installing and using this skill.
To create a PRD from a feature idea, provide a detailed problem statement, scope, goals, and acceptance criteria. The skill generates a structured PRD with success criteria, milestones, and risks, saving it as a JSON file in the /plans directory.
A product requirements document for scoping includes Objective, Problem Statement, Scope, Success Criteria, Metrics, Milestones, Risks, and Assumptions. This structure ensures stakeholders share a single vision and reduces ambiguity across the product team.
To ensure your PRD captures all requirements and user stories, the skill asks guided clarifying questions during generation. It prompts for missing details like constraints and acceptance criteria to validate the complete product scope before outputting the final JSON file.
You can start generating a PRD without full acceptance criteria upfront. The skill will prompt you with guided clarifying questions to gather missing details, ensuring the final product requirements document contains all necessary validation plans and scope definitions.
PRD generation includes versioning metadata for change tracking within the output JSON file. This ensures that as your product requirements evolve, you can monitor updates to objectives, scope, milestones, and risks throughout the discovery phase.
Use automated PRD generation during product discovery and requirements gathering to turn vague ideas into structured documents quickly. It helps articulate problem statements and define success criteria efficiently, reducing misalignment across stakeholders compared to manual documentation.
brandonburrusGenerates structured PRDs with goals, user stories, requirements, and metrics.
vitoropereiraConvert PRD markdown and task files into executable JSON configurations.
DergaczConvert Product Requirements Documents into prioritized development roadmaps with milestones.
VictorHueniGenerate a complete PRD from scratch with built-in validation of required fields.
