prd

Generate a comprehensive PRD from a feature brief using a structured template.

632|201|Updated Jun 21, 2018
One-click install
npx skills add https://github.com/garyexplains/examples --skill prd-garyexplains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/garyexplains/examples/tree/main/ralph/skills/prd
Command: npx skills add https://github.com/garyexplains/examples --skill prd-garyexplains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams quickly convert feature ideas and briefs into a structured PRD, ensuring clear scope and alignment.

Core Features & Use Cases

  • Clarifying questions (3-5) to resolve ambiguity in initial prompts.
  • PRD generation with standard sections: Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
  • Output artifact saved to tasks/prd-[feature-name].md for traceability and version control.

Quick Start

Provide a feature brief describing the problem and desired outcome, for example: "Add offline mode to the notes app." The skill will generate a complete PRD and save it to the tasks folder as tasks/prd-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a complete PRD from a brief feature description?

To generate a PRD, provide a concise feature brief describing the problem and desired outcome. The tool asks 3-5 clarifying questions to resolve ambiguity, then outputs a comprehensive document saved as tasks/prd-[feature-name].md.

What sections are included in a standard product requirements document for new features?

A standard PRD includes Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions sections to ensure clear scope and alignment.

Can I create user stories and acceptance criteria directly from a short project brief?

Yes, you can create user stories and acceptance criteria from a short project brief. The tool processes your brief and automatically structures these elements into the comprehensive PRD output alongside other functional requirements.

How do clarifying questions help refine functional requirements during PRD generation?

Clarifying questions help refine functional requirements by resolving ambiguity in initial prompts. The tool generates 3-5 questions about your brief to ensure the final PRD accurately captures the intended scope and technical considerations.

Does the generated PRD document get saved automatically for version control?

The generated PRD document is saved automatically for version control. It is stored as a markdown file named tasks/prd-[feature-name].md within the tasks folder, ensuring traceability for product teams planning new features.

What is the best way to document non-goals and success metrics for product management?

The best way to document non-goals and success metrics is using a structured PRD template. This tool automatically generates these standard sections alongside technical considerations and open questions from your initial feature briefing.