Create a technical implementation plan from a feature specification.

Input: Optionally specify a change name. If omitted, infer from context or ask. Anything else the user adds (a preferred stack, a constraint) is input to the plan.

Steps

Select the change and load artefacts

Load specs/changes/<name>/spec.md. If it does not exist, prompt to use the spec-kit-specify skill first.

Also load FRAMEWORK.md (with FRAMEWORK.local.md when present), the capability documents it links to for the enabled standards, the specs/features/ relevant to the area being changed, and the decision records in specs/decisions/ that govern it.
Research unknowns

If the spec contains unresolved [NEEDS CLARIFICATION] markers, pause and suggest using the spec-kit-clarify skill first unless the user explicitly wants to proceed.

List the plan's own unknowns — a dependency to choose, an integration pattern, a behaviour of the existing code — and settle each by reading the code or the dependency's documentation. Record each settled unknown under ## Decisions & Rationale with the alternatives considered.

spec-kit-plan