skills.rest
thrawn01
thrawn01COMMUNITY
Explore all skills by this author →
Website𝕏@thrawn01GitHub

prd-create

Guide a discovery session to elicit product requirements and write them to docs/features/{feature}/prd.md.

11|Updated Sep 5, 2025
Search Tags:#documentation#writing#adr#discovery#prd#stakeholders#product-requirements
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill prd-create-thrawn01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-create
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/prd-create
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill prd-create-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides a back-and-forth discovery session to elicit feature requirements and ensures a structured PRD is produced at the end, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured questioning: Elicits goals, constraints, success metrics, and risks from stakeholders.
  • Decision logging: Tracks agreements, open questions, and trade-offs to a single PRD.
  • PRD generation: Writes the final document to docs/features/{feature}/prd.md and records any ADRs if needed.
  • Use Case: As a product lead, you start with a napkin sketch and, after a focused dialogue, end with a complete PRD ready for review.

Quick Start

Begin a guided discussion to elicit requirements and finalize the PRD at docs/features/{feature}/prd.md.

Frequently Asked Questions about prd-create

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

FAQPage Schema
How do I write a product requirements document from a rough idea?▼

To write a product requirements document (PRD) from a rough idea, engage in a guided discovery session that elicits goals, constraints, and success metrics, then captures those decisions into a structured PRD file.

What is the best way to elicit product requirements from stakeholders?▼

Eliciting product requirements from stakeholders is best handled through structured, interactive questioning that tracks agreements, open questions, and trade-offs directly into a single PRD.

How do I update an existing PRD when new technical findings emerge?▼

You update an existing PRD by revising the document during a follow-up discovery session, integrating new information and technical findings to modify the original product requirements file.

When should I log architectural decisions alongside my PRD?▼

You should log architectural decisions alongside your PRD when stakeholder agreements or trade-offs warrant them, recording these ADRs to ensure technical context is preserved with the feature requirements.

Where are generated PRD files saved in my project directory?▼

Generated PRD files are saved directly to docs/features/{feature}/prd.md, providing a structured location for your finalized product requirements and any associated decision logs.

Related Skills

Explore More Product & Management Skills→
ZxelaZxela

discovery

Convert rough ideas into PRD, ADR, Technical Design, and Wireframes via guided dialogue.

Community
Advanced
sunLeeesunLeee

prd-generator

Convert vague feature requests into structured PRD documents saved as tasks/{feature}-prd.md.

Community
Intermediate
GeargrindadminGeargrindadmin

architecture

Analyze architectural trade-offs and document decisions with ADR templates.

Community
Intermediate
lorenzogmlorenzogm
15

bmad-agent-pm

Create Product Requirements Documents through user interviews and stakeholder alignment.

Community
Advanced