speckit-specify

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

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-specify-ahmedragabrg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/AhmedRagabRG/academy/tree/main/frontend/.agents/skills/speckit-specify
Command: npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-specify-ahmedragabrg

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 inside a spec-kit project, complete with user scenarios, functional requirements, success criteria, and a quality checklist. ## Core Features & Use Cases - Specification Generation: Parses a feature description into actors, actions, data, and constraints, then writes a full spec following the project's spec-template. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria (up to 3 iterations). - Clarification Management: Limits ambiguity to a maximum of 3 [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml, including optional git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login for enterprise users" and receives a numbered feature directory (e.g., specs/003-oauth2-login) containing a validated spec.md ready for /speckit-plan. ## Quick Start Ask the agent to 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 requirements, scenarios, 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 markers are allowed, and each is presented as a structured multiple-choice question for the user to resolve.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing templates and configuration. It reads .specify/init-options.json for feature numbering mode and optionally .specify/memory/constitution.md for project principles.

Can speckit-specify create a git branch automatically?▼

Branch creation is handled by an optional before_specify hook defined in .specify/extensions.yml, typically provided by a git extension. The core command always creates the spec directory and file itself, independent of any branch naming.

What happens if the generated spec fails validation?▼

The spec is checked against a quality checklist covering content quality, requirement completeness, and feature readiness. Failing items trigger spec updates and re-validation for up to 3 iterations, after which remaining issues are documented in the checklist notes.