Slice

A slice is a scoped design doc covering one technical vertical of a parent spec. It contains the HOW — file paths, libraries already in use, data shapes, sequences, contracts — but no code. It exists between spec (WHAT/WHY) and the task layer; the slice itself stops at design.

When to use

• A spec exists and needs design before it can be decomposed.
• One vertical of a feature is non-trivial and needs implementation choices made before any tasks are written.
• Multiple verticals are entangled and need to be untangled before estimation.

When NOT to use

• The spec is missing or vague — write or fix the spec first.
• The work is small enough to go straight to a single task.
• The change is a code-level refactor inside one file with no cross-cutting choices.

Output location

Derive from the parent spec path. Slices live in a slices/ directory next to the spec.