speckit-specify

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

5|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-specify-theonlytruebigmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/theonlytruebigmac/n-central-rest-api-mcp/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-specify-theonlytruebigmac

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, 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 and mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: Describe a feature 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 the clarify or plan phase. ## Quick Start Run the speckit-specify skill with a feature description such as "add user authentication with OAuth2" to create the feature specification.

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 skill with your feature description as the argument. It generates a short name, creates a numbered directory under specs/, copies the resolved spec-template to spec.md, and fills in user scenarios, requirements, and success criteria.

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

Spec-kit is a specification-driven development workflow using a .specify/ project structure. The specify command turns a natural language feature description into a validated spec.md file, which downstream commands like plan and tasks consume.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory. It reads .specify/init-options.json for numbering mode, .specify/memory/constitution.md for governance, and .specify/extensions.yml for hooks.

How many clarification questions can the spec contain?▼

The skill limits [NEEDS CLARIFICATION] markers to a maximum of 3 per specification. Each marker is presented to the user as a question with suggested answer options in a table, and the spec is updated with the chosen answers.

Why is my spec directory named differently from my git branch?▼

Spec directory naming and git branch naming are independent by design. The directory uses sequential or timestamp prefixes from init-options.json, while branch creation is handled separately by an optional before_specify hook.