PRD Generation
How AI generates product requirement docs
One of Flowback's most powerful features is automatic PRD (Product Requirement Document) generation. After each feedback conversation, the AI analyzes the entire exchange and produces a structured document that your team can act on immediately.
What's in a PRD
Every generated PRD follows a consistent structure designed to give your team all the information they need:
- Title — A concise summary of the feedback item
- Problem Statement — A clear description of the issue or need expressed by the submitter
- User Story — A "As a [user], I want [goal] so that [benefit]" formulation of the request
- Steps to Reproduce — For bug reports, a numbered list of steps to reproduce the issue
- Expected vs. Actual Behavior — What should happen versus what actually happens
- Impact Assessment — How severe the issue is, how many users are affected, and any workarounds available
- Acceptance Criteria — Clear conditions that define when the issue is resolved or the feature is complete
- Reporter — The name and email of the person who submitted the feedback
Codebase context
When you have GitHub connected, the PRD generation becomes even more powerful. The AI can:
- Reference relevant source files that might be related to the reported issue
- Include recent commit history that may be connected to the feedback
- Suggest which areas of the codebase might need changes
This codebase context is built by indexing your repository's file tree, README, and recent commits. The AI uses this to provide more specific, actionable PRDs that save your engineering team time on investigation.
Priority suggestion
Alongside the PRD, the AI also suggests a priority level for the submission. This suggestion is based on:
- The severity of the issue described
- The number of users likely affected
- Whether workarounds exist
- Your custom priority rules (if configured)
The suggested priority is included in the submission and automatically applied to any Linear issues created. See the Priority System docs for more on configuring this.
PRDs in Linear
When a Linear issue is created from a submission, the full PRD markdown is included in the issue description. This means your team sees the structured requirements directly in Linear without needing to navigate back to Flowback.
The issue description also includes:
- A reference number for cross-referencing
- Links to any uploaded screenshots
- Source and category labels
Multi-item PRDs
When using Auto-Split or Split & Review mode, the AI generates a separate PRD for each distinct feedback item identified in the conversation. Each PRD is self-contained and creates its own Linear issue with its own priority and labels.
See the Multi-Feedback docs for more details on how multiple issues are detected and processed.