Engineering
To PRD
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
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.
Process
-
Explore the repo to understand the current state of the codebase.
-
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones.
-
Write the PRD using the template below, then publish it to the project issue tracker.
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>
## Implementation Decisions
A list of implementation decisions that were made.
Do NOT include specific file paths or code snippets.
## Testing Decisions
A list of testing decisions that were made.
## Out of Scope
A description of the things that are out of scope for this PRD.
## Further Notes
Any further notes about the feature.