Full-Stack Feature

Delivers a feature as a working vertical slice instead of disconnected pieces.

Process

1. Define before coding (5 minutes that save an hour)

• User story: as a , I want , so that .
• Acceptance criteria: 3–6 checkable statements ("user sees X after Y").
• Out of scope: what this feature explicitly does NOT do.
• Ask ONLY the questions that would change the implementation; infer the rest and state your assumptions.

2. Thin vertical slice first

Get the narrowest possible end-to-end path working: DB field → API returns it → UI shows it. Confirm it runs. THEN enrich. Never build the whole backend before proving the UI wiring.

3. Layer by layer

Data (see database-schema)

• Model the entity + relations, migration, seed data for testing.