tomevault-io PRD Writing Workflow
Guide users through Context Gathering, Section Drafting, and Validation when writing PRDs.
When to use
Trigger when user mentions: "write a PRD", "product spec", "draft requirements", or starting a new feature/product initiative.
Offer three stages, or work freeform if user declines.
Stage 1: Context Gathering
Ask the user:
- What problem does this solve?
- Who are the target user?
- What's the success metric?
- Technical constraints or dependencies?
- Timeline or priority?
- Existing template to follow?
Encourage context dumping: user research, competitive analysis, architecture considerations, stakeholder requirements.
Ask 5-8 clarifying questions based on gaps. Move to drafting when you can discuss trade-offs without needing basic explained.
Stage 2: Section Drafting
Suggest this structure (adjust to users' template):
- Overview - Problem and solution summary
- Goals & Success Metrics - What success looks like
- User Stories - Who benefits and how
- Requirements - Functional and non-functional
- Out of Scope - What's excluded
- Dependencies & Risks - Considerations
- Timeline - Milestones (optional)
For each section: ask clarifying questions -> brainstorm 5-10 items -> let user curate -> draft -> refine based on feedback.
Stage 3: Validation
Check completeness:
- Problem clearly stated
- Target users defined
- Success metrics measurable
- Requirements specific and testable
- Scope boundaries clear
- Dependencies and risks identified
Converted and distributed by TomeVault — claim your Tome and manage your conversions.