Skip to content
cccskills
FreePublished on GitHub

write-prd

Write a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Overview

Based on Shape Up by Ryan Singer (Basecamp). A PRD defines the problem, the appetite, and the solution boundaries - not a detailed spec. The key insight from Shape Up: fix the time, flex the scope. Define how much the team is willing to spend before deciding what to build.

Workflow

Step 1: Set the Appetite

Before writing requirements, define the appetite - how much time is this worth?

  • Small batch: 1-2 weeks
  • Big batch: 4-6 weeks

If the solution requires more time than the appetite allows, cut the scope - don't extend the time.

Step 2: Write the Problem Statement

One paragraph. Answer: what is broken or missing today, who is affected, and what is the cost of not solving it. Avoid mentioning solutions here.

Step 3: Write the Pitch (Shape Up format)

Structure:

# PRD: [Feature Name]
**Appetite:** [Small batch / Big batch]
**Status:** Draft
**Author:** [your name]

## Problem
[What's broken, who's affected, cost of inaction]

## Solution
[Fat marker sketch - broad strokes, not pixel-perfect]

## Rabbit Holes
[Specific technical or design traps to avoid]

## No-Gos
[Explicitly what this does NOT include]

Step 4: Write the Solution at the right altitude

Shape Up's "fat marker sketch" principle: describe the solution broadly enough that engineers have room to make decisions. Over-specifying kills ownership and slows delivery.

Write requirements at the level of: "Users can do X" - not "There is a button in the top-right corner."

Step 5: Define Rabbit Holes

List specific traps the team could fall into. Examples:

  • "Don't rebuild the notification system - use existing infrastructure"
  • "Don't support bulk operations in v1"

Step 6: Define No-Gos

Explicit list of what this does NOT cover. This is the most important section for scope control.

Step 7: Add Open Questions

Format:

Q: [question]
Owner: [name]
Due: [date]

Anti-Patterns

1. Specifying solutions in the problem statement Bad: "We need to add a modal because users don't see the CTA." Good: "30% of users drop off at checkout. The CTA is not visible enough."

2. No appetite defined Bad: PRD with requirements but no time boundary. Good: "This is a small batch - 2 weeks max. If the solution needs more, cut scope."

3. Missing No-Gos Bad: PRD with only what's included. Good: Explicit No-Gos that prevent scope creep during build.

4. Over-specified requirements Bad: "The button is blue, 48px, positioned top-right with 16px margin." Good: "Users can trigger X from the main action area." (Let design decide the details.)

Quality Checklist

  • Appetite is defined (small or big batch)
  • Problem statement explains "why", not "what"
  • Solution is at the right altitude - no pixel-level specs
  • Rabbit holes are listed
  • No-Gos are explicit
  • Open questions have owners and due dates

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

The English summary is being prepared. Showing the original description.

qa-aman/claude-skills21Updated Oct 19, 2026

See all skills by qa-aman

Report a problem with this skill