prd

Generate structured PRDs with requirements, metrics, and acceptance criteria.

191|29|Updated Sep 2, 2025
One-click install
npx skills add https://github.com/juanandresgs/claude-system --skill prd-juanandresgs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/juanandresgs/claude-system/tree/main/skills/prd
Command: npx skills add https://github.com/juanandresgs/claude-system --skill prd-juanandresgs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs) and feature specifications, ensuring clear product direction and alignment.

Core Features & Use Cases

  • Structured PRD Generation: Creates detailed PRDs including problem statements, goals, non-goals, user journeys, requirements (P0/P1/P2), success metrics, and open questions.
  • Acceptance Criteria: Defines clear, testable acceptance criteria in Given/When/Then or checklist format.
  • Use Case: A product manager needs to define a new user authentication feature. They use this Skill to generate a PRD that outlines the problem of insecure logins, defines user journeys for sign-up and login, specifies P0 requirements for email/password authentication, and sets success metrics like a reduction in password reset requests.

Quick Start

Use the prd skill to write a product requirements document for a new user profile editing feature.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a product requirements document with structured user stories and acceptance criteria?

To create a product requirements document, this Skill generates structured PRDs featuring problem decomposition, user journey mapping, P0/P1/P2 requirement prioritization, and acceptance criteria in Given/When/Then or checklist format.

What should be included in a feature specification to ensure clear product direction?

A feature specification should include problem statements, goals, non-goals, user journeys, prioritized requirements, success metrics, and open questions to ensure clear product direction and alignment across stakeholders.

Can I use this PRD generator with AI planning agents for requirement analysis?

Yes, this PRD generator integrates with AI planning agents to perform requirement analysis, supporting problem decomposition and structured feature specification generation within existing product management workflows.

What is the best way to define and prioritize requirements in a PRD?

The best way to define requirements in a PRD is through P0/P1/P2 prioritization, categorizing core features as P0, secondary features as P1, and future enhancements as P2 to establish clear development boundaries.

How do I define testable acceptance criteria for product management requirements?

To define testable acceptance criteria for product management requirements, this Skill formulates them in Given/When/Then format or as detailed checklists, ensuring each requirement has clear, verifiable validation conditions.

When do I need to map user journeys in a product requirements document?

You need to map user journeys in a product requirements document when defining new features, allowing you to outline touchpoints like sign-up and login flows before specifying P0 requirements and setting success metrics.