skills.rest
sunLeee
sunLeeeCOMMUNITY
Explore all skills by this author →
GitHub

prd-generator

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

Updated Mar 19, 2026
Search Tags:#workflow#documentation#requirements#prd#product-management#user-stories
One-click install
npx skills add https://github.com/sunLeee/optimization --skill prd-generator-sunleee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-generator
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/scaffolding/prd-generator
Command: npx skills add https://github.com/sunLeee/optimization --skill prd-generator-sunleee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguous feature requests often lead to misaligned expectations and project delays. This skill clarifies requirements and produces a structured PRD to guide development.

Core Features & Use Cases

  • Clarification Workflow: prompts 3-5 targeted questions to derive precise requirements.
  • PRD Generation: outputs a complete PRD file saved at tasks/{feature}-prd.md.
  • Reusable Template: provides a standard PRD structure (overview, goals, user stories, functional & non-functional requirements, scope, design considerations, tests, milestones).

Quick Start

Provide a feature description and let the system generate a PRD by asking clarifying questions and saving to tasks/{feature}-prd.md.

Frequently Asked Questions about prd-generator

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

FAQPage Schema
How do I turn vague feature requests into a structured PRD?▼

To turn vague feature requests into a structured PRD, provide the initial request to trigger a 3-5 question clarification workflow that refines requirements into a comprehensive document with user stories and acceptance criteria.

What should a product requirements document include for sprint planning?▼

A product requirements document for sprint planning should include an overview, goals, user stories, functional and non-functional requirements, acceptance criteria, scope, design considerations, tests, and milestones.

How do I clarify ambiguous product requirements before writing documentation?▼

You clarify ambiguous product requirements by applying a targeted clarification workflow that asks 3-5 specific questions, ensuring precise requirements are captured before generating the final documentation draft.

Can I automatically save a generated PRD draft to a specific file path?▼

Yes, you can save a generated PRD draft automatically by directing the output to the specified file path tasks/{feature}-prd.md, making it readily available for sprint planning and team access.

What is the best way to document user stories and acceptance criteria?▼

The best way to document user stories and acceptance criteria is using a standardized PRD template that structures these elements alongside functional requirements and scope to guide development.

Why do ambiguous feature requests cause project delays?▼

Ambiguous feature requests cause project delays because they lead to misaligned expectations between teams, which a structured PRD prevents by clarifying exact requirements before development begins.

Related Skills

Explore More Product & Management Skills→
silaslopes100silaslopes100

reversa-researcher

Convert raw product ideation data into structured user personas and customer journey maps.

Community
Intermediate
busboom-software-studiobusboom-software-studio
1

create-tickets

Convert architecture-update.md and usecases.md into sequenced tickets with dependencies.

Official
Advanced
archerliarcherli

user-story-mapping-workshop

Guide product managers through adaptive user story mapping workshops.

Community
Intermediate
arimunandararimunandar
1

Interview Patterns

Codify a requirement-gathering workflow using AskUserQuestion before executing tasks.

Community
Basic