prd

Generates structured PRD documents from feature descriptions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams translate vague feature ideas into concrete PRDs that guide design, development, and alignment across stakeholders.

Core Features & Use Cases

  • Automated clarifying questions to resolve ambiguity and capture requirements.
  • Structured PRD generation with sections for Introduction, Goals, User Stories, Functional & Non-Goals, and Success Metrics.
  • Saves the PRD to a tracked file location for versioning and collaboration.

Quick Start

Provide a feature description and any constraints, and let the tool generate a complete PRD document 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 structured PRD from a feature description?

To generate a structured PRD, provide a feature description and any constraints. The tool asks 3–5 clarifying questions to resolve ambiguity, then outputs a document with Introduction, Goals, User Stories, Functional, Non-Goals, and Success Metrics sections.

What sections are included in a standard product requirements document?

A standard PRD includes Introduction, Goals, User Stories, Functional requirements, Non-Goals, and Success Metrics. These sections guide design, development, and cross-functional alignment for early-stage feature planning.

How do I scope early-stage feature ideas for cross-functional alignment?

Scoping early-stage feature ideas for cross-functional alignment involves answering automated clarifying questions to capture requirements. This translates vague concepts into concrete user stories and structured goals for stakeholders.

Can I save a PRD to a file for versioning and collaboration?

Yes, you can save a PRD to a file for versioning and collaboration. The generated document is automatically saved to the `/tasks/prd-[feature-name].md` directory as a Markdown file.

What is the best way to translate vague feature ideas into concrete requirements?

The best way to translate vague feature ideas into concrete requirements is through guided clarification. Automated questions resolve ambiguity and capture constraints, producing a structured PRD that guides development.