product-specification

name	product-specification
description	Use to create or review PRDs, BRDs, FRS documents, user stories, acceptance criteria, role models, journeys, information architecture, status models, KPI catalogues or feature tickets. Do not use after the specification is already approved unless behaviour changes.

Product Specification

1. Start from the management or user outcome.
2. Define scope, non-goals, users, roles and terminology.
3. Describe current and target behaviour.
4. Define workflows, statuses, business rules, permissions, data, integrations, reporting and complete failure states.
5. Write acceptance criteria that are observable and testable.
6. Trace every feature to a decision or requirement.
7. Separate launch requirements from later options.
8. Record assumptions and unresolved decisions.

Required outputs may include:

PRD | BRD | FRS | User stories | Acceptance criteria
Information architecture | Role model | Status model | KPI catalogue | Tickets

A specification is complete when implementation and verification can proceed without inventing material behaviour.