prd

Draft a structured PRD with goals, user stories, and success metrics.

5|1|Updated Jun 7, 2020

Search Tags:#planning #specification #prd #user-stories #acceptance-criteria #product-requirements

Ready to run

npx skills add https://github.com/mseok/dot --skill prd-mseok

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mseok/dot/tree/main/ai/codex/skills/prd
Command: npx skills add https://github.com/mseok/dot --skill prd-mseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to translate ideas into a concrete, actionable plan that engineers and stakeholders can execute against.

Core Features & Use Cases

Structured PRD with sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics.
Clarifying questions to resolve ambiguity before drafting the PRD.
Generated PRD is saved to tasks/prd-[feature-name].md for traceability and handoff.

Quick Start

Describe the feature in detail and I will generate a complete PRD document 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 draft a comprehensive product requirements document for a new feature?▼

To draft a product requirements document, provide a detailed feature description to generate a structured PRD with goals, user stories, functional requirements, non-goals, and success metrics saved as a markdown file for handoff.

What sections should be included in a PRD for software development?▼

A PRD for software development should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design considerations, Technical considerations, and Success Metrics to guide feature delivery and stakeholder alignment.

How do I write user stories and acceptance criteria for feature planning?▼

Write user stories and acceptance criteria by providing a feature description; the tool formalizes requirements into structured PRD sections like US-001 and FR-1 to resolve ambiguity and guide engineering teams.

Does generating a PRD require predefined technical specifications or design documents?▼

Generating a PRD does not require predefined technical specifications; you provide a feature description, and clarifying questions resolve ambiguity before drafting the complete product requirements document.

What is the best way to formalize product requirements for engineering handoff?▼

The best way to formalize product requirements for engineering handoff is generating a comprehensive PRD saved to tasks/prd-[feature-name].md, ensuring traceability across product management, design, and engineering teams.