speckit-specify

Invoke the speckit-specify command followed by your feature description in natural language. The skill generates a short name, creates a numbered directory under specs/, and writes a spec.md based on the resolved spec-template.

The workflow parses your description, extracts actors and requirements, fills user scenarios and success criteria, then validates the result against a quality checklist. Up to three NEEDS CLARIFICATION markers may be presented as multiple-choice questions before finalizing.

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

Branch creation is delegated to an optional before_specify hook defined in .specify/extensions.yml, typically from the git extension. The spec directory and spec.md file are always created by the core command itself, independent of branch naming.

Markers appear when a requirement significantly impacts scope, security, or user experience and no reasonable default exists. The skill limits these to three, presents suggested answers in a table, and replaces markers after you respond.

Generated specs rely on informed guesses documented in an Assumptions section, so domain-specific constraints may need manual review. Validation retries are capped at three iterations, after which remaining issues are only flagged in the checklist notes.