to-prd

Files (1)

• SKILL.md

SKILL.md (first lines)

This skill takes the current conversation context and code understanding and produces a PRD. DO NOT interview the user — just synthesize what you already know.

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

## Process

1. Explore the repository to understand the current code state, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD and respect any ADRs in the affected area.

2. Sketch the seams at which you'll test the functionality. Prefer existing seams over new ones. Use the highest possible seam. If new seams are needed, propose them at the highest point you can.

Check with the user that these seams match their expectations.

3. Write the PRD using the template below and then publish it to the project's issue tracker (e.g., GitHub Issues, Jira, Trello, GitLab). Apply the `ready-for-agent` triage label — no additional triage needed.

<prd-template>

## Problem Statement

The problem 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 story must be in the format:

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

<user-story-example>
1. As a digital banking customer, I want to see my account balances, so that I can make more informed spending decisions.
</user-story-example>

This list of user stories must be extremely comprehensive and cover all aspects of the functionality.

## Implementation Decisions

A list of implementation decisions that were made. This may 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. These can become outdated very quickly.

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

## Testing Decisions

A list of testing decisions that were made. Include:

- A description of what makes a good test (test only external behavior, not implementation details)
- Which modules will be tested
- Prior reference artifacts for the tests (e.g., similar types of tests in existing code)

## Out of Scope

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

## Additional Notes

Any additional notes about the functionality.

</prd-template>

From hcb2019/claude-code-skills, MIT.

More from hcb2019/claude-code-skills