speckit-specify

Generates validated feature specifications from natural language descriptions using spec-kit templates.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-specify-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-specify
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-specify-tjsasakifln

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 automates the creation of structured spec files that are ready for planning and implementation. ## Core Features & Use Cases - Spec Generation: Creates a feature directory and spec.md from a natural language description, with automatic short-name and numbering (sequential or timestamp). - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria (max 3 iterations). - Clarification Handling: Limits ambiguity to 3 [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Extension Hooks: Supports before_specify and after_specify hooks via .specify/extensions.yml for branch creation and post-processing. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a complete, validated spec at specs/003-oauth2-login/spec.md ready for /speckit-plan. ## Quick Start Ask the AI to create a feature specification for your idea, for example: run speckit-specify with the description "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 the speckit-specify command with a natural language feature description. 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.

How does spec-kit handle unclear requirements in a specification?▼

The workflow allows a maximum of 3 [NEEDS CLARIFICATION] markers, prioritized by scope, security, and UX impact. Each marker is presented as a structured multiple-choice question, and the spec is updated with your selected answers before re-validation.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing templates and optionally init-options.json, memory/constitution.md, and extensions.yml. Specs are written to a specs/ directory by default.

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

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

What happens after a specification is created and validated?▼

The spec passes through a quality checklist covering content quality, requirement completeness, and feature readiness. Once validated, it is ready for the next phase commands such as /speckit-clarify or /speckit-plan.