skills.rest
nrminor
nrminorCOMMUNITY
Explore all skills by this author →
GitHub

prd

Generate a structured PRD with clarifying questions and save it to a markdown file.

Updated Nov 2, 2024
Search Tags:#project management#documentation#feature planning#prd#product requirements#PRD generation#clarifying questions
One-click install
npx skills add https://github.com/nrminor/.dotfiles --skill prd-nrminor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/nrminor/.dotfiles/tree/main/.config/.claude/skills/prd
Command: npx skills add https://github.com/nrminor/.dotfiles --skill prd-nrminor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs provide a clear, structured blueprint for new features, aligning teams and stakeholders and reducing rework by capturing goals, success criteria, and dependencies up front.

Core Features & Use Cases

  • Clarifying questions: Asks 3-5 essential questions to resolve ambiguity before drafting the PRD.
  • PRD generation: Produces a complete document with sections such as Introduction/Overview, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
  • Saving and reuse: Saves the generated PRD to tasks/prd-[feature-name].md for easy tracking and versioning.
  • Use Case: You describe a feature like "dark mode for mobile app," and the skill returns a ready-to-edit PRD you can hand to an engineering team.

Quick Start

Use the prd skill to generate a PRD for a new feature described by the user and save it to 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 create a structured PRD from a feature idea?▼

A PRD—Product Requirements Document—translates feature ideas into structured blueprints. This Skill generates one by asking clarifying questions about your feature, then produces a complete document with sections like Goals, User Stories, Functional Requirements, Design Considerations, and Success Metrics, saved as a markdown file ready for team review.

What sections does a generated PRD include?▼

The PRD includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions. Each section captures essential details—what the feature solves, who uses it, how it works technically, and how success is measured.

Can I use this to document features without external tools?▼

Yes. This Skill requires no external dependencies or integrations—it generates and saves the PRD directly to your repository as a markdown file (tasks/prd-[feature-name].md), making it immediately shareable and version-controlled with no additional setup.

What happens after I describe my feature?▼

The Skill asks 3–5 clarifying questions to resolve ambiguity—scope, user personas, constraints, success criteria—then drafts a complete, ready-to-edit PRD document that aligns stakeholders and provides your engineering team a clear specification to build from.

What's the difference between this and writing a PRD manually?▼

Manual PRDs are time-consuming and risk inconsistent structure. This Skill accelerates the process by prompting for essential details upfront, then auto-generating a consistent, professionally structured document in minutes rather than hours.

Related Skills

Explore More Product & Management Skills→
tobyileetobyilee
24

prd

Generate structured PRDs with requirements, user stories, and acceptance criteria.

Community
Advanced
CoreStack-EnggCoreStack-Engg

techspec-generator

Generate a Technical Specification .docx from a PRD or Action Plan.

Official
Advanced
0xHoneyJar0xHoneyJar
4

planning-sprints

Converts PRDs and SDDs into structured sprint plans with tasks and dependencies.

Official
Advanced
YSheldonYSheldon

product-manager

Generate PRDs, user stories, and roadmaps from context inputs.

Community
Intermediate