← Files Product & App ArchitectARCHIVED FILE

references/feature-specs.md

946 Bytes · Nov 22, 2026 · 18:42 UTC

↓ Download file

See the change to this file →

# Feature Delta Specifications

For existing products, write a **delta spec**: goal, current behavior, affected entry points, new flow, states, role/permission changes, data/API effects, dependencies, migration/rollout, non-goals and acceptance criteria.

## State matrix
Map initial, loading, empty, success, validation-error, dependency-error, offline/retry and permission-denied only as applicable. Define preservation of partial input and recoverability.

## Acceptance
Each required behavior needs an observable test: Given setup, When action, Then visible outcome and persistent side effect (or no side effect). Cover negative paths and auth boundaries. Never invent current endpoints/tables from an unseen repo.

## Rollout
Check backward compatibility, schema evolution, feature flags where warranted, metric instrumentation, accessibility, rollback and support impact. Don't add an architecture migration for a small feature by default.

SHA-256: 38b1b61fc97a690a8dd1fc8279700bf0edf7499d49b45e0ba35e0b2fc1e2aca8