speckit-specify

Generates a validated feature specification from a natural language description in spec-kit projects.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-specify-secrakib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/secrakib/rag-eval-project/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-specify-secrakib

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 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 and writes a structured spec.md using the project's resolved spec-template, with numbered feature directories under specs/. - Quality Validation: Creates a requirements checklist and iteratively validates the spec against content quality, requirement completeness, and readiness criteria, with up to 3 clarification questions for ambiguous points. - Extension Hooks: Executes before_specify and after_specify hooks defined in .specify/extensions.yml, including mandatory git branch creation hooks. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a ready-to-plan specification at specs/003-oauth2-login/spec.md with measurable success criteria. ## Quick Start Ask the agent to create a feature specification by describing your feature, for example: create a spec for adding user authentication with OAuth2 to the API.

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 specify command with your feature description as the argument. The Skill parses actors, actions, and constraints, then writes a complete spec.md with user scenarios, functional requirements, and success criteria into a new directory under specs/.

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

The Skill inserts up to 3 [NEEDS CLARIFICATION] markers only for decisions that significantly impact scope, security, or user experience. It then presents each question with suggested answer options in a table and updates the spec based on your choices.

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 and .specify/memory/constitution.md for project principles if present.

Can I customize the feature directory name or numbering?▼

Yes, you can explicitly provide SPECIFY_FEATURE_DIRECTORY to override the default. Otherwise the Skill auto-generates a directory under specs/ using either a timestamp or sequential 3-digit prefix based on the feature_numbering setting in init-options.json.

What happens after the specification is written?▼

The Skill validates the spec against a quality checklist stored in checklists/requirements.md, runs any after_specify extension hooks, and reports the feature directory and spec file path. The spec is then ready for /speckit-clarify or /speckit-plan.