From spec to release, step by step. For every feature.

  1. 01

    Agree the spec's ground rules

    Architecture, accessibility, performance budget, and the security and privacy baseline, agreed once.

  2. 02

    Write each feature spec

    Each feature as stories and acceptance criteria, with its threat model and the data it collects.

    Never skipped
  3. 03

    Split the plan into tasks

    Architecture, dependencies and tests, split into tasks that each meet a criterion.

  4. 04

    Build and verify each feature

    Engineers and supervised agents build to the tasks; each release ships a criterion-by-criterion report.

  5. 05

    Change the spec first

    A new requirement, risk or review finding becomes a spec change first, then code.

Spec-driven frontend development

Each part of the method, in full

The spec pack, the criteria, the reports and the gates, written out for the engineers who will review our work.

Spec templates you can copyField notes

The frontend stack we ship with. Chosen per project.

  • React
  • TypeScript
  • Next.js
  • Astro
  • NestJS
  • Tailwind CSS
  • Radix UI
  • shadcn/ui
  • Figma
  • Storybook
  • Playwright
  • Vitest
  • Jenkins
  • Argo CD

Product names and logos are trademarks of their owners.

web/appzshrelease-2.1
~/web/app$npx playwright test
4 of 4 files
auth/session.spec.ts14 tests6.1s
consent/storage.spec.ts9 tests4.8s
security/headers.spec.ts11 tests3.2s
forms/purpose.spec.ts22 tests9.7s
Test files4 passed(4)
Tests56 passed(56)
Donein 41.2s
~/web/app$