Slice Design

Load the spec-writing standard first. The inputs are the nlspec and the current code; the outputs are vertical slices, each carrying an ephemeral slice spec. The slice spec is authoritative for its slice only, then archived in the PR — never maintained. It may contain nothing with cross-slice lifetime (the lifetime rule).

Slicing

Slice vertically: each slice crosses the stack thinly and yields something exercisable early — curl-able, browsable, claim-demonstrable. Reject horizontal stack-order plans (migrations → services → API → frontend); that is the default model tic, and under it nothing is touchable until the end. Sequence slices so each demonstrates at least one claim or de-risks a seam, and so no slice cuts across a seam mid-contract.