doc-prd

Generate a structured markdown PRD file from a guided conversation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sunLeee/optimization --skill doc-prd-sunleee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-prd
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/scaffolding/docs/doc-prd
Command: npx skills add https://github.com/sunLeee/optimization --skill doc-prd-sunleee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collecting and structuring user requirements into a clear, actionable PRD can be time-consuming and error-prone. This skill guides conversations to capture the essential details and produces a structured PRD that aligns stakeholders and accelerates product development.

Core Features & Use Cases

  • Interactive requirement elicitation through guided questions to define problem, users, scope, success criteria, and constraints.
  • Automated PRD generation with a standardized markdown template stored at tasks/{feature}-prd.md, including in-scope/out-of-scope, milestones, and acceptance criteria.
  • Use Case: Given a feature idea, the skill outputs a complete PRD draft ready for review and versioned updates.

Quick Start

Provide a feature name and respond to prompts to generate a PRD draft in tasks/{feature}-prd.md.

Frequently Asked Questions about doc-prd

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

FAQPage Schema
How do I generate a PRD from a feature idea conversation?

To generate a PRD from a feature idea, provide the feature name and respond to guided clarifying questions. The skill processes your inputs to produce a structured markdown PRD file with defined scope, goals, and milestones.

What sections are included in a generated product requirements document?

A generated product requirements document includes sections for in-scope features, out-of-scope items, goals, milestones, and success metrics. This standardized markdown template ensures stakeholders align on product scope and development constraints.

Can I use conversation-based requirement gathering for product scoping?

Yes, you can use conversation-based requirement gathering for product scoping by answering interactive questions. This workflow captures essential details like problem definition, target users, and success criteria to structure your product discovery process.

What's the best way to structure out-of-scope items in a PRD draft?

The best way to structure out-of-scope items in a PRD draft is using the automated markdown template. It separates in-scope and out-of-scope sections automatically, ensuring clear boundary definition for feature development and stakeholder alignment.

Where does the generated PRD markdown file get saved?

The generated PRD markdown file is saved at tasks/{feature}-prd.md. This standardized output path organizes your product requirements documents by feature name, making them ready for version control and subsequent review.