Reference
Specification types
| Type | Category | Examples |
|---|---|---|
| User Experience | Product | Page flows, behaviour, validation rules |
| User UI | Product | Layout, copy, components used |
| API Contract | Technical | Endpoint contracts, request and response shapes |
| Data Model | Technical | Entities, fields, relationships |
| Third Party Dependency | Technical | New vendor or library dependencies |
| Service Architecture | Technical | Service boundaries or cross-service changes |
| Use Case Logic | Technical | Business rules and workflow behavior |
| Deployment Strategy | Operational | Releases, feature flags, migrations |
| Custom | Custom | Anything that does not fit a standard type |
Every specification has a before and an after. The before describes the current state. The after describes the desired state once the iteration is shipped.