TemplatesAI workspace

Product requirements breakdown

Work Last updated:

A PRD skeleton: goals, user scenarios, scope, non-functionals, acceptance, schedule.

How to use

  1. Write the success metric before splitting features.
  2. Keep "Out of scope" filled in to stop scope creep.
  3. Run Simplify for a one-page summary before review.

Outline preview

  • Requirement name
  • Background and goals
  • Problem to solve
  • Success metric
  • User scenarios
  • Scenario A
  • Role / trigger / expected result
  • Scenario B
  • Role / trigger / expected result
  • Scope
  • In this release
  • Feature 1
  • Feature 2
  • Out of scope
  • Explicit exclusion
  • Non-functional
  • Performance / security / compatibility
  • Acceptance criteria
  • Verifiable condition 1
  • Verifiable condition 2
  • Schedule
  • Review / dev / integration / launch
View Markdown source
# Requirement name
## Background and goals
- Problem to solve
- Success metric
## User scenarios
### Scenario A
- Role / trigger / expected result
### Scenario B
- Role / trigger / expected result
## Scope
### In this release
- Feature 1
- Feature 2
### Out of scope
- Explicit exclusion
## Non-functional
- Performance / security / compatibility
## Acceptance criteria
- Verifiable condition 1
- Verifiable condition 2
## Schedule
- Review / dev / integration / launch

Loading calls no AI — the template is only handed over locally; Undo restores your previous content.