speckit-specify

Generates a validated feature specification from a natural language description.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-specify-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/speckit-specify
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-specify-base-analitica

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 natural 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, including user scenarios, requirements, and success criteria. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for branch creation and post-processing. - Use Case: Type a feature idea like "add OAuth2 login" and receive a numbered feature directory (e.g., specs/003-oauth2-login) containing a validated specification ready for $speckit-plan. ## Quick Start Run the speckit-specify skill with a short description of the feature you want specified, such as asking it to create a specification for user authentication.

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 with spec-kit?▼

Run the speckit-specify command followed by your feature description in natural language. It generates a numbered directory under specs/ containing a spec.md built from the active spec-template, plus a quality checklist.

What does the speckit-specify command generate?▼

It generates a feature directory (e.g., specs/003-user-auth) containing spec.md with user scenarios, functional requirements, success criteria, and key entities, plus a checklists/requirements.md validation file. It also records the path in .specify/feature.json.

Does speckit-specify require a spec-kit project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory for templates, init-options.json, and optional extensions.yml. Without this structure, template resolution and feature numbering cannot work.

How are feature directories numbered in spec-kit?▼

Numbering follows .specify/init-options.json: sequential mode assigns the next 3-digit number (e.g., 003), while timestamp mode uses YYYYMMDD-HHMMSS. The short name is appended after the prefix.

What happens when a specification has unclear requirements?▼

The skill marks critical ambiguities with [NEEDS CLARIFICATION] markers, limited to 3 maximum. It presents each question with suggested answer options in a table, waits for your choices, then updates the spec and re-validates.