From spec to release, step by step. For every feature.
- 01
Agree the spec's ground rules
Architecture, accessibility, performance budget, and the security and privacy baseline, agreed once.
- 02
Write each feature spec
Each feature as stories and acceptance criteria, with its threat model and the data it collects.
Never skipped - 03
Split the plan into tasks
Architecture, dependencies and tests, split into tasks that each meet a criterion.
- 04
Build and verify each feature
Engineers and supervised agents build to the tasks; each release ships a criterion-by-criterion report.
- 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.
The spec pack: constitution, spec, plan, tasks
A spec pack is four versioned documents: the constitution sets the rules, the spec says what each feature must do, the plan says how we build it, and the tasks break it into small, checkable units. Code, tests and reviews all trace back to them.
Read moreAcceptance criteria for frontends, in Given/When/Then
An acceptance criterion describes one behaviour a user can observe, written as Given a starting state, When an action, Then a result. Every criterion we write becomes an automated test, so the spec is checked on every change, not once at the end.
Read moreTrace reports: every criterion, its test and its result
A trace report is a table generated from the test run: every acceptance criterion in the spec, the test that covers it and whether it passed. It ships with every milestone and release, so you can check what was delivered without reading the code.
Read moreAgent-assisted delivery, constrained by the spec
We use supervised coding agents to deliver like a larger team. They build only from tasks in the spec, a senior engineer reviews every change before it merges, and only tools the client approves in writing ever see the client's code.
Read moreQuality gates every change passes before merge
A quality gate is a check that must pass before a change can merge. Every change we ship passes six: its acceptance tests, security, privacy, accessibility, a performance budget and a senior review. A change that fails any of them does not merge.
Read moreSpec Kit or OpenSpec: greenfield and brownfield
We use GitHub Spec Kit for new products, where a full spec is written per feature, and OpenSpec for existing codebases, where every change is a delta against a living spec. Both are open source and produce plain files, so the client is never locked into our tools.
Read more
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.