write-prd

Draft a structured PRD from a brief or problem statement.

19|3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/qa-aman/claude-skills --skill write-prd-qa-aman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/pm/write-prd
Command: npx skills add https://github.com/qa-aman/claude-skills --skill write-prd-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a Product Requirements Document (PRD) from a brief or problem statement, turning vague ideas into a structured planning artifact.

Core Features & Use Cases

  • Converts briefs or feature ideas into a complete PRD with problem, appetite, and solution boundaries.
  • Produces a Shape Up–style PRD structure including Problem, Solution, Rabbit Holes, No-Gos, Appetite, and Open Questions to guide engineering handoff.
  • Facilitates alignment among product, design, and engineering by providing a ready-to-share document.

Quick Start

Provide a brief problem statement or feature idea and a target appetite to generate the PRD.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I turn a product brief into a structured PRD for engineering handoff?

A Shape Up–style PRD organizes product planning into Problem, Appetite, Solution, Rabbit Holes, No-Gos, and Open Questions sections. This structure clarifies scope boundaries and risks to ensure engineering teams understand exactly what to build.

What is the best way to document rabbit holes and no-gos in product requirements?

Use a Shape Up–style PRD structure to explicitly list rabbit holes and no-gos in product requirements. This prevents scope creep by defining out-of-scope complexities and excluded features, ensuring engineering teams avoid designated pitfalls during implementation.

Can I generate a product requirements document from just a short problem statement?

Yes, you can generate a product requirements document from a short problem statement or feature pitch. Providing the initial idea and a target appetite produces a complete PRD with defined problem statements, solution boundaries, and open questions.

How do I write a PRD using the Shape Up methodology?

Writing a PRD using the Shape Up methodology involves structuring sections for Problem, Appetite, Solution, Rabbit Holes, No-Gos, and Open Questions. This converts vague product ideas into a structured planning artifact aligned for engineering handoff.

Does a Shape Up PRD include an appetite section for feature planning?

Yes, a Shape Up PRD includes an appetite section for feature planning. Providing a target appetite alongside your brief defines the time allocation and solution boundaries for the proposed product idea within the generated document.