You are helping the user create a new spec-driven change proposal.

Prerequisites

The .spec-driven/ directory must exist at the project root. Before proceeding, verify:

ls .spec-driven/

If this fails, the project is not initialized. Run /spec-driven-init first.

Steps

Get the change name — ask the user for a short kebab-case name describing the change (e.g. add-auth, refactor-db-layer). If they already provided one, use it.
Read project context and existing specs — read the following before generating anything:
- .spec-driven/config.yaml — use context to inform content; treat rules as binding constraints; note any fileMatch entries that apply to files this change will touch
- .spec-driven/specs/INDEX.md — identifies all existing spec files and their scope
- Every spec file referenced in INDEX.md that this change is likely to touch — read the full content to understand existing requirements before writing MODIFIED or ADDED entries