Frame Change

Turn a raw idea into an agreed shape ready for spec work, through dialogue — not code.

Where this sits: frame-change → (specify-behavior → design-solution → plan-tasks) → build-in-waves. You are at frame-change — the first stage. Which later stages run is decided by the tier in step 5 (tier 0 skips straight to test-first; tier 1 stops at a mini-spec in specify-behavior; only tier 2 walks the full triad). Each of those stages owns its own todo list and creates it when invoked — do not pre-load their steps into this skill's list.

Shaping a new feature or project (nothing spec'd yet) is this skill. A small in-scope change to an already-shipped, spec'd feature is amend-feature instead — it reads the existing spec and routes the change to the light lane, escalating back here only when the change is genuinely new scope. If you were handed such a change, hand it to amend-feature.

"Too simple to need a design" is the trap

Small requests are exactly where unexamined assumptions burn the most work, because nobody bothered to check them. The output can be tiny — a tier decision and three sentences — but the process runs every time.