to-prd

name	to-prd
description	Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

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.

A repository can hold multiple PRDs at once, each in its own directory under .agent-state/prds/<slug>/.

.agent-state/ is local-only and not committed to the repo. It is gitignored and exists only on the current machine. PRDs written here are working state for agents — never reference .agent-state/ paths from committed artifacts (source code, PR descriptions, commit messages, issues, RFCs, or repo docs). If the PRD needs to be shared, publish it to the issue tracker or a docs system; don't link to the local path.

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 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. Pick a slug for the PRD.

Generate a short kebab-case slug from the PRD's problem statement (e.g. multi-prd-support, account-balance-widget). The slug is the directory name under .agent-state/prds/.

Then check .agent-state/prds/ for a collision:

• No collision → create .agent-state/prds/<slug>/ and write the PRD there.
• Collision, and the current conversation is iterating on the existing PRD → update that PRD in place. If the directory already contains issue-*.md files, confirm with the user before overwriting.
• Collision, but the conversation is about a different topic that happens to produce the same slug → append a numeric suffix (<slug>-2, <slug>-3, …) and use that.

4. Write the PRD to <repository-root>/.agent-state/prds/<slug>/PRD.md using the template below.

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 , I want a , so that

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

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.

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.