speckit-specify

Generate a validated feature specification from a natural language feature description.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-specify-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/speckit-specify
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-specify-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone. This Skill converts a plain-language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria, ready for planning. ## Core Features & Use Cases - Spec Generation: Creates a feature directory under specs/ with a spec.md built from the resolved spec-template, using sequential or timestamp-based numbering. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Runs optional or mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: Type a feature idea like "add OAuth2 login for the mobile app" and receive a numbered spec directory containing a stakeholder-ready specification and a quality checklist, prepared for /speckit-plan. ## Quick Start Ask the assistant to create a feature specification by describing your feature, for example: create a spec for adding user authentication with OAuth2.

Frequently Asked Questions about speckit-specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a feature specification from a text description?▼

Invoke the specify command with your feature description as the argument. The skill generates a short name, creates a numbered directory under specs/, writes spec.md from the resolved template, and validates it against a quality checklist.

What is spec-kit and how does the specify command fit in?▼

Spec-kit is a spec-driven development workflow where features start as specifications. The specify command is the first step, producing spec.md, which downstream commands like /speckit-plan and /speckit-tasks consume via .specify/feature.json.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing the template resolution stack. It optionally reads .specify/extensions.yml for hooks, .specify/memory/constitution.md for principles, and .specify/init-options.json for numbering.

How are feature directories numbered in spec-kit?▼

Numbering is controlled by feature_numbering in .specify/init-options.json. Sequential mode assigns the next 3-digit number like 003-user-auth, while timestamp mode uses a YYYYMMDD-HHMMSS prefix. Sequential is the default when the setting is absent.

What happens when a spec has unclear requirements?▼

The skill inserts up to 3 [NEEDS CLARIFICATION] markers for critical ambiguities, then presents each as a question with suggested answer options in a table. After the user responds, it updates the spec and re-runs validation.

Why did my specify run skip the git branch creation?▼

Branch creation is handled only by a before_specify hook from the git extension, not by the core command. If .specify/extensions.yml is missing, has no enabled before_specify hook, or the hook has a condition, branch creation is skipped.