SteffenCarlsen To PRD
Create a PRD from existing context. Do not restart discovery unless the context is too thin to write a useful spec.
Process
- Inspect the relevant repo area if the PRD depends on current code behavior.
- Use existing project vocabulary, conventions, ADRs, and issue labels when visible.
- Ask only for blocking product decisions. Skip interviews when the conversation already contains enough detail.
- Identify the highest practical test boundary for the feature. Prefer existing seams over new ones.
- Draft the PRD. Publish it to the available issue tracker only when the user asked for publishing or the tracker/tooling is clearly configured.
PRD Template
## Problem Statement
Describe the user-facing problem.
## Solution
Describe the user-facing solution.
## User Stories
1. As an <actor>, I want <capability>, so that <benefit>.
## Implementation Decisions
- Capture modules, interfaces, schema/API contracts, behavior rules, and important constraints.
- Avoid file paths unless a specific path is itself part of the decision.
## Testing Decisions
- State the behavior to prove.
- Name the test boundary and similar existing coverage if found.
## Out of Scope
- List explicit non-goals.
## Further Notes
- Capture unresolved risks, dependencies, or follow-ups.