Take the conversation and the codebase and produce a spec. Do NOT interview the user — synthesise what you already know. When the work was big enough for grilling, this runs after it; either way, the decisions are already made.

The triage label vocabulary should have been provided to you.

The spec is the only artefact nothing makes fail

Lint fails. The suite fails. The adversarial reviewer rejects the PR. The spec does not — and the reviewer cannot cover it, because it checks the code against the spec and takes the spec as ground.

So a wrong premise in a spec walks through implementation green, review green and adversarial review green, and surfaces weeks later. Everything below exists to give the spec a half that can be checked before a line of code exists.

Establish the present

Read where reading answers it, measure where it does not. The user answers neither.

to-spec

The spec is the only artefact nothing makes fail

Establish the present