to-prd

This skill takes the current conversation context and codebase understanding and generates a PRD. Do not interview the user—just synthesize what you already know.

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview 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。

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. If you have not already explored the repository, explore it to understand the current state of the codebase. Use the project's domain glossary terms throughout the PRD, and respect any ADRs for the areas you are modifying.

   Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.

2. Outline the main modules you need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested independently.

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

   A deep module (as opposed to a shallow module) is one that encapsulates a large amount of functionality behind a simple, testable, and rarely changing interface.

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.

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

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

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

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

Problem Statement

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

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

Solution

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

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

User Stories

A long, numbered list of user stories. Each user story is formatted as:

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

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

   As an , I want a , so that

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

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

Implementation Decisions

A list of implementation decisions made. This can include:

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

• Modules to be built/modified

  The modules that will be built/modified

• Module interfaces to be modified

  The interfaces of those modules that will be modified

• Technical clarifications from the developer

  Technical clarifications from the developer

• Architecture decisions

  Architectural decisions

• Schema changes

  Schema changes

• API contracts

  API contracts

• Specific interactions

  Specific interactions

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

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

Exception: if the prototype produced a snippet that encodes a decision more precisely than words can (state machine, reducer, schema, type shape), inline it within the relevant decision and briefly note that it came from the prototype. Trim it down to the decision-rich parts—not a runnable demo, just the important parts.

Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Testing Decisions

A list of testing decisions made. Include:

A list of testing decisions that were made. Include:

• A description of what constitutes a good test (test only external behavior, not implementation details)

  A description of what makes a good test (only test external behavior, not implementation details)

• Which modules will be tested

  Which modules will be tested

• Precedents for testing (i.e., similar types of tests in the codebase)

  Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

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

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

Further Notes

Any further notes about the feature.

Any further notes about the feature.