speckit-specify

Invoke the specify command with your feature description as the argument. The skill extracts actors, actions, and constraints, then writes a spec.md file with user scenarios, functional requirements, and success criteria into a new specs/ directory.

Spec-kit is a specification-driven development workflow where features are specified before planning and implementation. The specify command is the first step, producing a validated spec.md that downstream commands like /speckit-plan and /speckit-tasks consume.

Yes, it requires a spec-kit project with a .specify/ directory containing templates and configuration. It reads .specify/init-options.json for feature numbering and .specify/memory/constitution.md for project principles if present.

Directories are named with a prefix plus a short name, such as 003-user-auth. The prefix is either a sequential three-digit number or a timestamp, controlled by the feature_numbering setting in .specify/init-options.json.

The skill inserts up to 3 [NEEDS CLARIFICATION] markers for critical decisions, then presents each as a structured question with suggested answer options. After you respond, it updates the spec and re-runs validation.

Validation fails when the spec contains implementation details, untestable requirements, or non-measurable success criteria. The skill automatically revises the spec up to 3 iterations and documents remaining issues in the checklist notes.