1---
2name: to-prd
3description: Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.
4---
5 
6This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
7 
8## Process
9 
101. Explore the repo to understand the current state of the codebase, if you haven't already.
11 
122. 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.
13 
14A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
15 
16Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
17 
183. Write the PRD using the template below and submit it as a GitHub issue.
19 
20<prd-template>
21 
22## Problem Statement
23 
24The problem that the user is facing, from the user's perspective.
25 
26## Solution
27 
28The solution to the problem, from the user's perspective.
29 
30## User Stories
31 
32A LONG, numbered list of user stories. Each user story should be in the format of:
33 
341. As an <actor>, I want a <feature>, so that <benefit>
35 
36<user-story-example>
371. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
38</user-story-example>
39 
40This list of user stories should be extremely extensive and cover all aspects of the feature.
41 
42## Implementation Decisions
43 
44A list of implementation decisions that were made. This can include:
45 
46- The modules that will be built/modified
47- The interfaces of those modules that will be modified
48- Technical clarifications from the developer
49- Architectural decisions
50- Schema changes
51- API contracts
52- Specific interactions
53 
54Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
55 
56## Testing Decisions
57 
58A list of testing decisions that were made. Include:
59 
60- A description of what makes a good test (only test external behavior, not implementation details)
61- Which modules will be tested
62- Prior art for the tests (i.e. similar types of tests in the codebase)
63 
64## Out of Scope
65 
66A description of the things that are out of scope for this PRD.
67 
68## Further Notes
69 
70Any further notes about the feature.
71 
72</prd-template>
73