to-prd

---
name: to-prd
description: Turn the current conversation context into a PRD draft. Use when user wants to create a PRD from the current context; publish it to an issue tracker only after explicit approval.
---

This skill takes the current conversation context and codebase understanding and produces a PRD draft. Do NOT interview the user to fill gaps — synthesize what you already know and record material assumptions or open questions in the draft.

If the user explicitly approves publication, the issue tracker and triage label vocabulary must be known first. Ask the maintainer for any missing project-specific tracker or label mapping before publishing.

## Process

1. 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. Sketch out the major modules likely to be built or modified 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.

Record uncertain module or testing choices as assumptions or open questions; do not interrupt the synthesis to interview the user.

3. Write the PRD using the template below and present it as a draft. Publish it to the project issue tracker, and apply the mapped `ready-for-agent` triage label, only after the user explicitly approves that external action.

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

• LICENSE.txt 1 KB
• SKILL.md 3 KB