prd

Generate structured Product Requirements Documents with user stories and acceptance criteria.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/stephschofield/beth --skill prd-stephschofield
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/stephschofield/beth/tree/main/.github/skills/prd
Command: npx skills add https://github.com/stephschofield/beth --skill prd-stephschofield

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document from scratch is time-consuming and often produces vague requirements that developers cannot implement. This Skill turns a rough feature idea into a structured, actionable PRD with numbered requirements and verifiable acceptance criteria. ## Core Features & Use Cases - Clarifying Questions: Asks 3-5 targeted questions with lettered options so users can answer quickly (e.g., "1A, 2C, 3B") before any document is written. - Structured PRD Generation: Produces a complete PRD with goals, user stories, functional requirements, non-goals, technical considerations, success metrics, and open questions. - Implementation-Ready Stories: Each user story includes verifiable acceptance criteria sized for a single focused work session, written for junior developers or AI agents. - Use Case: You have an idea for a task priority feature. Describe it, answer a few multiple-choice questions, and receive a complete PRD saved to tasks/prd-task-priority.md ready for your development team. ## Quick Start Ask the agent to create a PRD for your feature idea, then answer its clarifying questions to receive a structured requirements document saved in the tasks folder.

Frequently Asked Questions about prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PRD for a new feature?▼

Describe your feature idea and the skill asks 3-5 clarifying questions with lettered options. After you answer, it generates a structured PRD with goals, user stories, and functional requirements saved to tasks/prd-[feature-name].md.

What sections should a product requirements document include?▼

A complete PRD includes an overview, measurable goals, user stories with acceptance criteria, numbered functional requirements, non-goals, design and technical considerations, success metrics, and open questions. This structure keeps scope clear and implementation unambiguous.

How do I write acceptance criteria that developers can verify?▼

Write criteria as specific, testable statements rather than vague claims. For example, use "Button shows confirmation dialog before deleting" instead of "works correctly", and include checks like typecheck passing and browser verification for UI stories.

Does the PRD skill implement the feature after writing requirements?▼

No, the skill explicitly stops after creating the PRD document. It only gathers requirements, asks clarifying questions, and saves the Markdown file to the tasks directory, leaving implementation as a separate step.

When should I not use a full PRD for a feature?▼

Skip the full PRD for trivial bug fixes, small configuration changes, or exploratory prototypes where formal requirements add overhead without value. The PRD format is designed for features needing clear scope boundaries and multiple user stories.