Write a PRD
A PRD that is finished because it is grounded, not because it is long.
Write the PRD from research, screens, personas, and metrics already in the workspace, with sources on every requirement.
What is happening
You point at a flow, a persona, or a metric miss. Kopilot drafts a PRD with sources on each requirement, then keeps that trail when the work becomes tickets, so engineering does not inherit a thinner story.
The gap
Specs read complete and cite nothing. Review becomes taste.
What Kopilot does
Kopilot drafts the PRD from the map: problem, evidence, requirements, and the trail to tickets.
What you leave with
A document you can argue with, because every line has a source.
How this use case works
Point at the work
A flow, a persona, a metric miss. Not a blank “write a PRD” prompt.
Before and after screens are the evidence, not decoration.
Draft with citations
Goals, non-goals, requirements, and the screens they came from.
The PRD draft lists requirements with a source on each line.
Handoff without thinning
Tickets keep the same sources so engineering does not inherit a thinner story.
Handoff keeps those sources so tickets are not a thinner rewrite.
- Cited requirements
- Problem and evidence up front
- A path into tasks
