Understanding PRDs
What's inside a Scriptonia-generated PRD and how to use each section.
Anatomy of a Scriptonia PRD
Every PRD generated by Scriptonia follows a consistent structure designed for modern product teams.
Overview
A one-paragraph summary of the product or feature — useful for sharing with stakeholders who don't need all the detail.
Goals & Success Metrics
What the feature is trying to achieve and how success will be measured. Scriptonia generates OKR-aligned goals when possible.
User Stories
Written in standard "As a [user], I want to [action], so that [benefit]" format. These feed directly into the ticket generation step.
Functional Requirements
What the system must do. Numbered for traceability back to tickets.
Non-Functional Requirements
Performance, security, scalability, and accessibility considerations.
Acceptance Criteria
Testable, binary conditions that define "done". Scriptonia writes these in Gherkin-style (Given/When/Then) when complexity warrants it.
Out of Scope
Explicitly lists what is NOT being built. Prevents scope creep and aligns engineering expectations.
Open Questions
Flags assumptions that need validation before engineering begins.