skills.rest
jaydubya818
jaydubya818COMMUNITY
Explore all skills by this author →
GitHub

prd

Generate structured PRD markdown files from feature prompts.

Updated Mar 26, 2026
Search Tags:#planning#templates#requirements#prd#product-management#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill prd-jaydubya818
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/prd
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill prd-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD Generator helps teams convert vague ideas into structured documents that clearly define goals, success criteria, and scope to align stakeholders and guide development.

Core Features & Use Cases

  • Clarifying Questions: prompts users to answer 3-5 critical questions to resolve ambiguity.
  • PRD Structure: produces a complete PRD with sections: Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, Open Questions.
  • Output & Storage: saves the generated PRD to tasks/prd-[feature-name].md for traceability and versioning.
  • Single-Source of Truth: ensures all decisions are captured in a unified document suitable for reviews.

Quick Start

Describe your feature in detail, and I will generate a complete PRD at 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 structured PRD with user stories and acceptance criteria?▼

To generate a structured PRD, describe your feature in detail and the tool will output a complete markdown file with sections for User Stories, Functional Requirements, and acceptance criteria to reduce ambiguity.

What sections should a product requirements document include for stakeholder reviews?▼

A product requirements document for stakeholder reviews should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.

How do I convert vague feature ideas into a standardized PRD format?▼

You can convert vague ideas into a standardized PRD format by providing a feature prompt; the tool will ask 3-5 clarifying questions to resolve ambiguity and then generate the document.

Can I use this to create product management templates for new projects?▼

Yes, you can use this for new projects as it automates the creation of product management templates, enforcing a standardized PRD structure to align stakeholders and guide development.

Where are generated PRD files saved for versioning and traceability?▼

Generated PRD files are saved as markdown files to the tasks/prd-[feature-name].md directory path, ensuring traceability and versioning for your project documentation.

Related Skills

Explore More Product & Management Skills→
danielcastro-devdanielcastro-dev

speclet-draft

Draft collaborative feature plans with clarifying questions to .speclet/draft.md.

Community
Intermediate
OmexITOmexIT
13

ticket-breakdown

Convert PRD or design docs into epics, tickets, and acceptance criteria.

Community
Intermediate
JingyiWngJingyiWng

bmad-create-epics-and-stories

Decompose product requirements into epics and stories with acceptance criteria.

Community
Advanced
davzuckydavzucky

prd

Generate a structured Product Requirements Document and save it to /tasks/prd-[feature-name].md.

Community
Advanced