0.15 — one question per round, and Spec Kit when it is there

0.15 — one question per round, and Spec Kit when it is there

The interview contract now asks one frontier question per round and ends the turn on it. A live run on 2026-09-11 batched six questions with recommended answers into one message and then proceeded as if they were decided; the user never answered one. The contract already said to wait, but a batched list with recommendations reads as a proposal. No answer now pauses the interview — no Big, plan, Minis, or execution on an assumed answer — and a self-supplied answer is recorded as open. "Proceed without answering" is the only way a recommendation becomes a decision, with that instruction as its evidence. This is the third deliberate departure from grilling, recorded in docs/method.md. (#14)

When a repository already carries GitHub's Spec Kit — .specify/ plus installed speckit.* commands or speckit-* skills — the skill calls those commands wherever a step produces the artifact they write: constitution as a source, clarify into the frontier one question at a time, specify/plan/tasks for the artifacts, implement scoped to one Mini, analyze after checks, converge as one input to whole-journey verification. specify init is never run inside the workflow. Spec Kit's [X] marks are not proof; the Mini's own check is. Mapping is in references/speckit.md. (#13)

Not yet exercised: a live run under the one-question rule, and any run in a repository with Spec Kit on. Both are the next trials.