What problem does it solve?
This Skill transforms informal, natural-language feature descriptions into a complete, planning-ready feature specification and associated branch so teams can move from idea to planning without manual spec writing or checklist creation.
Core Features & Use Cases
- Generates a concise short name for the feature branch and invokes the project's create-new-feature script with appropriate flags (timestamp vs sequential) to create and check out the branch.
- Produces a specification file from the .specify/templates/spec-template.md by extracting actors, actions, data, constraints, user scenarios, functional requirements, success criteria, and key entities, and writes a quality checklist to FEATURE_DIR/checklists/requirements.md.
- Runs a checklist-driven validation loop (up to 3 iterations), surfaces up to three critical clarifications when needed, and reports branch name, spec path, and readiness; can surface optional or automatic extension hooks before and after specification.
- Use Case: Product managers or technical writers supply a short feature description and receive a branch with a validated spec and checklist, ready for planning or clarification.
Quick Start
Use /speckit.specify followed by a short natural-language description of the feature you want specified.
