prd

Generate a one-screen PRD with requirements, user stories, and constraints.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/benjaleivas/Claude-Code-Workflow --skill prd-benjaleivas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/benjaleivas/Claude-Code-Workflow/tree/main/skills/prd
Command: npx skills add https://github.com/benjaleivas/Claude-Code-Workflow --skill prd-benjaleivas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a structured PRD from a raw problem statement to align teams on goals, scope, and success criteria before planning.

Core Features & Use Cases

  • Automatic PRD generation from a described problem, capturing the Problem Statement, User Stories, and Requirements.
  • Structured template sections for P0-P2, Technical Constraints, Open Questions, and Success Criteria.
  • Use Case: A product manager provides a brief problem statement and the tool outputs a complete, review-ready PRD.

Quick Start

Describe the problem you want to solve, and let the tool generate a complete PRD draft ready for review.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a PRD from a problem statement?

To generate a PRD, provide a brief problem statement and the tool automatically outputs a structured document capturing the problem, user stories, requirements, and success criteria ready for team review.

What sections are included in a standard product requirements document template?

A standard PRD template includes sections for the problem statement, user stories, prioritized requirements from P0 to P2, technical constraints, open questions, success criteria, and a saved output path.

How do I write user stories and prioritize requirements for non-trivial work?

You write user stories and prioritize requirements by feeding a raw problem description into a PRD generator, which structures the scope into P0 to P2 tiers and captures actionable constraints before planning begins.

When do I need a product requirements document before planning development work?

You need a PRD before planning non-trivial development work when clear, actionable requirements, user stories, and technical constraints must be captured to align teams on goals, scope, and success criteria.

Can I automatically draft success criteria and technical constraints from a problem description?

Yes, you can automatically draft success criteria and technical constraints by processing a problem description through a PRD generator, which populates these specific sections to align teams on scope and goals.

What is the best way to structure open questions in a PRD for team alignment?

The best way to structure open questions in a PRD is to isolate them in a dedicated section within the template, ensuring unresolved technical constraints and scope inquiries are visible before planning begins.