To Prd

---
name: to-prd
description: Turn the current conversation context into a PRD for an initiative-scale effort and publish it to the GitHub Project. Use ONLY for a large, multi-issue initiative — for discrete work (a single feature or bug) file an issue directly or use to-issues instead.
---

This skill takes the current conversation context and codebase understanding and produces a PRD for an **initiative-scale** effort. Do NOT interview the user — just synthesize what you already know.

> **Scope (read first).** A PRD is not a new kind of artifact — it is just a regular **issue** whose body is a PRD spec, at initiative scale, that holds **sub-issues**. It sits *above* the slices only in the sub-issue sense (parent ▸ children), nothing more. For discrete intent (a single feature/bug/refactor), file an issue directly per `working-agreements.md`, or use `to-issues`; do **not** write a PRD — reaching for one on small work creates a second, competing intake path.

The issue/Project contract is set up by `github-project-setup` and recorded in `.claude/gh-project.json`.

## Process

1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain vocabulary from `CLAUDE.md` / `.claude/rules/glossary.md` throughout the PRD, and respect `.claude/rules/decisions.md` for the area you're touching.

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

3. Write the PRD using the template below, then publish it as an **issue whose body is the PRD** (per the `working-agreements.md` filing lifecycle). Set `Area` / `Priority`; set `Mode` = **`HITL`** — a PRD is an initiative spec, reviewed before its slices run. Its slices (created later via `to-issues`) become **sub-issues** of this issue and carry their own per-slice `Mode`.

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

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

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