Fullstack Product Specification

Use When

• Work spans UI and backend in one delivery slice
• Requirements are unclear, conflicting, or incomplete
• Teams need a shared source of truth before coding

Workflow

1. Capture business outcome, user roles, and success metrics.
2. Define journeys and states for each persona (happy path, empty, error, denied).
3. Specify API contracts, including request and response schemas, errors, and versioning.
4. Define domain and persistence impact (new entities, migration, indexing, retention).
5. Set non-functional requirements (latency, throughput, accessibility, security, auditability).
6. Record rollout strategy, migration or backfill needs, and rollback criteria.

Required Checks