Resolve ambiguities in a feature spec through focused, sequential questioning.

Input: Optionally specify a change name. If omitted, infer from context or ask. Anything else the user adds is context for prioritising the questions.

Run this before spec-kit-plan. If the user explicitly skips it (an exploratory spike, say), proceed, but warn that the risk of rework downstream increases.

Steps

Select the change

Auto-select if only one directory exists under specs/changes/. Otherwise ask.
Load specs/changes/<name>/spec.md

If it does not exist, prompt the user to use the spec-kit-specify skill first; never create a spec here. Also read FRAMEWORK.md (with FRAMEWORK.local.md when present) for the constraints the answers must respect.

spec-kit-clarify