write-a-prd

This skill creates a PRD and saves it to ./docs/<feature-name>/PRD.md. You may skip steps if context is already provided or you don't consider them necessary.

When invoked interactively (user at the keyboard)

1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.

1. Explore the repo to verify their assertions and understand the current state of the codebase.

1. 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 decisions one-by-one.

1. 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.

1. Once you have a complete understanding of the problem and solution, write the PRD using the template below.

When invoked by afk (context provided, no user interaction)

When called with [GRILLSUMMARY], [ROADMAPENTRY], or similar context blocks, skip the interview (steps 1–3) and synthesize the PRD directly from the provided context. Do not ask follow-up questions. Infer the feature name from the roadmap entry or context and slugify it (lowercase, hyphens) for the output path.

Output

Write the PRD to ./docs/<feature-name>/PRD.md. Create the directory if needed.

Wrap the PRD content in delimiters so automated tools can extract it:

<!-- PRD-START -->
(PRD content here)
<!-- PRD-END -->

<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:

1. As an <actor>, I want a <feature>, so that <benefit>

<user-story-example>

1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending

</user-story-example>

This list of user stories should be extremely extensive and cover all aspects of the feature. Always use numbered items (1., 2., 3.) — downstream tools reference stories by number.

Implementation 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

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>