specify-behavior

Produce docs/specs/<YYYY-MM-DD>-<feature>/requirements.md from the approved frame-change outcome. Requirements are the durable source of intent: they outlive this conversation, and every task, test, and commit will cite their IDs.

Two modes — pick by what you were handed

Tier-1 mini-spec — a fix plus a guard for an already-approved feature (you came from amend-feature or root-cause). You are not authoring a new requirements.md. Append to the owning feature's requirements.md (or docs/specs/fixes.md if no feature owns it):

• the fix requirement — one EARS criterion (Step 2's forms) for the corrected behavior;
• its SHALL CONTINUE TO guard — Step 3, for the behavior the fix must not break.