speckit-specify

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

2|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/guestgraph/engine --skill speckit-specify-guestgraph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/guestgraph/engine/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/guestgraph/engine --skill speckit-specify-guestgraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and inconsistent. 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 numbered feature directory under specs/ with a spec.md built from the resolved spec-template, covering user scenarios, requirements, success criteria, and key entities. - 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 before_specify and after_specify hooks from .specify/extensions.yml, including git branch creation, and persists the feature directory to .specify/feature.json for downstream commands. - Use Case: Type a feature idea like "add OAuth2 login to the API" and receive a validated, stakeholder-readable specification at specs/003-oauth2-api-integration/spec.md, ready for /speckit-plan. ## Quick Start Run /speckit-specify followed by a description of the feature you want to specify, such as "add 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/, writes spec.md from the spec-template, and validates it against a quality checklist.

What does the speckit-specify command produce?▼

It produces a feature directory like specs/003-user-auth containing spec.md and a checklists/requirements.md quality checklist. It also writes the feature directory path to .specify/feature.json so /speckit-plan and /speckit-tasks can locate it.

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

Yes, it requires a project initialized with spec-kit containing a .specify/ directory with templates and optionally memory/constitution.md and extensions.yml. Without this structure the template resolution and hook checks cannot run.

How are clarification questions handled during specification?▼

The spec allows a maximum of 3 [NEEDS CLARIFICATION] markers for decisions that significantly impact scope, security, or user experience. Each is presented as a question with suggested answer options in a table, and the spec is updated with your choices.

Can I control the feature directory numbering in spec-kit?▼

Yes, set feature_numbering in .specify/init-options.json to "sequential" for NNN prefixes or "timestamp" for YYYYMMDD-HHMMSS prefixes. You can also explicitly provide SPECIFY_FEATURE_DIRECTORY to override auto-generation.