speckit-specify

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

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill speckit-specify-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/speckit-specify
Command: npx skills add https://github.com/ArMaTeC/Redball --skill speckit-specify-armatec

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 numbered 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, resolving up to 3 clarification questions with the user. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for branch creation and post-processing automation. - Use Case: A product owner types a feature idea like "add OAuth2 login" and receives a complete, stakeholder-ready specification at specs/001-oauth2-login/spec.md with a validated quality checklist. ## Quick Start Run /speckit-specify followed by your feature description, for example: create a specification 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 with spec-kit?▼

Run /speckit-specify followed by your feature description in natural language. The command generates a short name, creates a numbered directory under specs/, and writes a spec.md file based on the resolved spec-template with scenarios, requirements, and success criteria.

How does speckit-specify handle unclear requirements?▼

It makes informed guesses using industry standards and documents assumptions, reserving [NEEDS CLARIFICATION] markers for critical decisions only. A maximum of 3 clarification questions are presented with suggested answer options in tables for the user to resolve.

Does speckit-specify create git branches automatically?▼

Branch creation is optional and handled by a before_specify hook from the git extension, not by the core command. The spec directory and spec.md file are always created by the command itself, independent of any git branch naming.

What project structure does speckit-specify require?▼

It requires a spec-kit project structure with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Feature numbering can be sequential (NNN) or timestamp-based (YYYYMMDD-HHMMSS).

Why does my specification fail the quality validation checklist?▼

Specs fail validation when they contain implementation details like frameworks or APIs, lack measurable success criteria, have untestable requirements, or miss acceptance scenarios. The command iterates up to 3 times to fix issues before warning the user.