markoblogo Spec To PRD
Convert current understanding into a durable PRD without re-running the whole discovery session.
Workflow
- Synthesize what is already known from the conversation and repo.
- Use the project's domain language and existing architectural decisions.
- Identify the highest useful seams for implementation and testing.
- Confirm only the few assumptions that would distort the PRD if wrong.
- Produce one PRD artifact:
- issue tracker body;
- markdown file;
- handoff-ready document.
PRD Shape
Include:
- problem statement;
- solution from the user's perspective;
- extensive user stories;
- implementation decisions;
- testing decisions;
- out of scope;
- further notes and open assumptions.
Rules
- Do not dump file paths unless they are durable anchors.
- Do not include code unless a small shape encodes a real decision more precisely than prose.
- Keep scope sharp; explicitly name what is out of scope.
- If discovery is too weak, route back to
rapid-grillingordoc-grounded-grillingfirst.
Final Report
State where the PRD lives, what assumptions remain, and the best next step: issue breakdown, prototype, or execution.