Write a prd

Skill shaunczubkowski/claude-skills/write-a-prd

Reusable Claude Code skills for agentic software development workflows.

Install

npx -y skills add shaunczubkowski/claude-skills --skill write-a-prd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create a PRD (Product Requirements Document) through user interview, codebase and LLM wiki exploration, and module design, then write a PRD in the project directory's `.claude` folder. User when user wants to write a PRD, create a product requirements document, or plan a new feature.

SKILL.md

3.0 KB, as published. Nobody here has run it

This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.

Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between deicisions one-by-one.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.

A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.

Check with the user that these modules match their expectations.
Check with the user which modules they want tests written for.

Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be saved to the project directory's .claude/PRD folder.

<prd-template>

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

As an <blank>, I want <blank>, so that I can <blank>.

Example

As an ice cream truck owner, I want a system that tracks my ice cream inventory, so that I can always have ice cream on hand.

This list of user stories should be extremely extensive and cover all aspects of the feature.

Impelementation Decisions

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Testing Decisions

ALL CODING IMPLEMENTATIONS MUST FOLLOW TEST DRIVEN DEVELOPMENT BEST PRACTICES

A list of testing decisions that were made. Include:

A description of what makes a good test (only test external behavior, not implementation details)
Which modules will be tested
Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this PRD.

Further Notes

Any further notes about the feature.

</prd-template>