Build

This skill makes two calls: how the work is cut into slices, and when a run of them stops. Everything else a slice goes through belongs to the route the task runs or to the repo's own rules: each slice is written and verified as code-writing says, and is accepted by design-review and committed as git says before the next one starts.

Cut the slices

A brief or a plan that already slices the work is the input, not a reason to skip this skill: take its slices in the order given, and keep the stop rules below. Otherwise cut the work yourself:

• Vertical, the default: one whole path through the stack, with its type, its implementation and its test.
• Contract-first: the schema and types land first, then each consumer as a slice of its own.
• Risk-first: the uncertain part goes first, so the plain parts build on something proven.

A slice is a path, never a layer. Good: POST /orders, the form that calls it, and one test. Bad: every endpoint, then every screen, then every test.

Stop and hand back

A run takes slice after slice with no reader in between, and its scope stays with whoever set it. Stop, and hand back to whoever coordinates the run, or else the owner, when: