42 lines (27 loc) · 1.17 KB

SPEC:

Copy to SPEC.md (or docs/specs/<feature>.md) and fill in. The best specs are self-contained: name the files and interfaces, state what's out of scope, and end with an end-to-end check that proves it works. Time spent here beats time spent watching the implementation.

Fast path: start a session and say "Interview me about using AskUserQuestion, then write the spec here." Then run the spec in a fresh session.

Goal

Context

Approach

Files to touch:
New interfaces / functions:
Dependencies (prefer existing — see the decision hierarchy):

Out of scope

Edge cases

Verification (success criteria)

Tests:
Build / typecheck passes:
Manual / e2e check:
Evidence to capture: