Create feature specifications from descriptions
speckit.specifycommandsetup L1★1
Giuseppe-Bianc/jsavrs ↗What it does
Create or update feature specification from natural language description
Best for
Agile teams converting informal feature requests into structured specs without heavyweight process overhead.
Inputs
- · Feature description (natural language, 1–10 sentences)
- · Optional: existing 00-context.md for template/feature name
Outputs
- · Spec file (path: specs/[number]-<short-name>/spec.md)
- · Branch: [number]-<short-name>
- · Quality checklist (specs/[number]-<short-name>/checklists/requirements.md)
- · [NEEDS CLARIFICATION] markers (max 3) for ambiguous scope/security/UX choices
Requires
- · .specify/scripts/powershell/create-new-feature.ps1
- · Git
Preconditions
- · .specify/templates/spec-template.md exists
- · specs/ directory initialized
- · Git repo with remotes configured
Failure modes
- · Short name already exists (branches/specs checked) — uses N+1 counter instead
- · No user scenarios identifiable — ERROR (spec scope too vague)
- · >3 [NEEDS CLARIFICATION] markers — user cuts scope to reduce ambiguity
Trust signals
- · Auto-extraction of 2–4 word short name from description
- · Checks all 3 sources (remote branches, local branches, specs/ dirs) for collision
- · Quality checklist generated automatically (not optional)
- · [NEEDS CLARIFICATION] limit enforced (max 3, prioritized by impact)