skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-prd

Write Product Requirements Documents using the Shape Up methodology with appetite, rabbit holes, and no-gos.

11|Updated Mar 20, 2026
Search Tags:#documentation#product management#prd#product requirements#scope control#feature spec#shape up
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --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/next-leap-claude-code/tree/main/.claude/skills/write-prd
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill write-prd-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often write PRDs that are over-specified, lack time boundaries, or suffer from scope creep. This Skill structures PRD writing around the Shape Up methodology, forcing clear problem statements, defined appetites, and explicit scope exclusions. ## Core Features & Use Cases - Shape Up PRD Structure: Generates PRDs with appetite (small/big batch), problem statement, fat-marker solution, rabbit holes, and no-gos. - Anti-Pattern Detection: Flags common PRD mistakes like solution-laden problem statements, missing time boundaries, and pixel-level over-specification. - Reusable Template: Ships a fill-in PRD template with sections for personas, success metrics, dependencies, and timeline. - Use Case: A PM needs to formalize a Smart Follow-Up feature idea. The Skill produces a scoped PRD with a 2-week appetite, explicit no-gos, and open questions with owners and due dates. ## Quick Start Ask the assistant to write a PRD for your feature idea using the write-prd skill, describing the problem and target users in one or two sentences.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I write a PRD using the Shape Up method?▼

Start by setting the appetite (small batch of 1-2 weeks or big batch of 4-6 weeks), then write a problem statement focused on what is broken and who is affected. Follow with a fat-marker solution sketch, rabbit holes, and explicit no-gos.

What is an appetite in a product requirements document?▼

An appetite is the fixed amount of time a team is willing to spend on a feature, such as a small batch of 1-2 weeks or a big batch of 4-6 weeks. If the solution exceeds the appetite, you cut scope rather than extend the timeline.

What should a PRD problem statement include?▼

A problem statement should be one paragraph covering what is broken or missing today, who is affected, and the cost of not solving it. It must avoid mentioning solutions, which belong in a separate section.

What are rabbit holes and no-gos in a PRD?▼

Rabbit holes are specific technical or design traps the team should avoid, like rebuilding existing infrastructure. No-gos are an explicit list of what the feature does not cover, which is the most important section for preventing scope creep.

When should I not over-specify requirements in a PRD?▼

Avoid pixel-level specifications like exact button colors, sizes, and positions. Write requirements at the level of user capabilities, such as "users can trigger X from the main action area", leaving design decisions to the team.

Related Skills

Explore More Product & Management Skills→
jupitermoneyjupitermoney

user-personas

Create three user personas from research data with JTBD, pains, and gains.

Official
Advanced
thesaifalitaithesaifalitai
8

project-manager

Plan agile software delivery with sprint backlogs, user stories, and release checklists.

Community
Advanced
Fantasia1999Fantasia1999

product-strategist

Generates aligned OKR cascades from company to team levels using Python scripts and scoring metrics.

Community
Advanced
imclabimclab
1

quick-design

Generate dated markdown Quick Design Specs for small gameplay or XR changes.

Official
Intermediate