to-prd

This skill uses the current conversation context and codebase understanding to generate a PRD.Do notinterview the user—just synthesize what you already know.

The issue tracker and triage label vocabulary should already be provided to you—if not, run /setup-matt-pocock-skills。

Process

Explore the repo to understand the current state of the codebase (if you haven't already done so). Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
Sketch out the seams at which you will test the feature. Prefer using existing seams over creating new ones. Use the highest seam possible. If a new seam is needed, propose it at the highest point you can find. The fewer seams in the codebase, the better—the ideal number is one.

Confirm with the user that these seams match their expectations.

Write the PRD using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label—no additional triage.

Problem Statement

The problem the user faces, from the user's perspective.

Solution

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

User Stories

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

As an , I want a , so that

This user story list should be very thorough, covering all aspects of the feature.

Implementation Decisions

A list of implementation decisions that have been made. Can include:

Modules to be built/modified
Module interfaces to be modified
Technical clarifications from the developer
Architecture decisions
Schema changes
API contracts
Specific interactions

Do not include specific file paths or code snippets. They may quickly become outdated.

Exception: If prototyping produced a code snippet that more precisely encodes a decision than words can (state machine, reducer, schema, type structure), include it inline in the relevant decision and briefly note that it comes from prototyping. Trim to the decision-dense parts—not a working demo, just what matters.

Testing Decisions

A list of testing decisions that have been made. Includes:

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

Out of Scope

A description of what is out of scope for this PRD.

Further Notes

Any further notes about the feature.