What is a vertical slice?
One end-to-end product outcome that touches every technical layer needed to make it work.
A vertical slice starts with something a user does and ends with something they can see. In between it passes through the interface, the application logic and the database. It is narrow, and it works.
The opposite is building in layers: finish the frontend, then the backend, then the database. Each layer can look finished while no user can complete a task. The risk of joining them stays hidden until late.
With agents this matters more, because an agent will finish a layer and report success. A slice gives it a result that can be tested from the outside.
Lessons that use it
- 03Stop building frontend, backend, then databaseThree finished layers can add up to nothing a user can do.
The ruleCut work by what a user can do, never by technical layer.
- 04Prove one complete path firstThe first slice exists to show you which of your assumptions are wrong.
The ruleBuild one thin, complete journey and test it end to end before you build wider.