Menu
Create spec.md from a feature description.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.
Use when local verification passed and the feature is ready to ship to Azure.
Use when a plan exists and the application source or IaC needs to be created or updated.
Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code.
Use when the user wants to run the full Specify → Plan → Implement → Deploy loop end-to-end in one shot. Accepts a free-form prompt that is passed to specify.
Use when implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying.
| name | specify |
| description | Create spec.md from a feature description. |
$ARGUMENTS
$ARGUMENTS is the feature description from the triggering message — assume it's available even if the placeholder appears literally above. Don't ask the user to repeat it unless they provided an empty command.
Load context. Read specs/constitution.md (principles, non-negotiables, out-of-scope) and run /speckit:constitution without specific principles automatically first, if the file is missing.
Create <feature_directory> under specs/, named <NNN>-<short-name>:
<NNN> — 3-digit zero-padded sequence, one greater than the highest existing prefix in specs/ (start at 001 if none).<short-name> — 2–4 words, lowercase, hyphen-separated, derived from the feature description.Write specs/feature.json with the feature directory path:
{ "feature_directory": "<feature_directory>" }
Create the spec based on assets/spec-template.md, stored in <feature_directory>/spec.md with these sections:
Guidelines: make informed defaults for unspecified details, marking genuine unknowns as [NEEDS CLARIFICATION: <question>]; focus on what and why — implementation details belong in plan.md; do not write code, choose a tech stack, or start implementation here.
Report the path to <feature_directory>/spec.md and a one-line summary.