speckit-specify

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

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-specify-marionoratorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/marionoratoRN/custom-speckit-flow/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-specify-marionoratorn

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 plain-language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria, then validates it against a quality checklist. ## 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, success criteria, and assumptions. - Quality Validation: Generates a requirements checklist and iterates on the spec until it passes, resolving up to three [NEEDS CLARIFICATION] markers through structured user questions. - Extension Hooks: Runs optional and mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login for enterprise users" and receives a complete, stakeholder-ready specification at specs/003-oauth2-login/spec.md, ready for planning. ## Quick Start Ask the assistant to run /speckit-specify followed by a description of the feature you want to specify.

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 a natural language description of the feature. The command generates a short name, creates a numbered directory under specs/, and writes a spec.md with user scenarios, functional requirements, and success criteria.

How does speckit-specify handle unclear requirements?▼

It makes informed guesses based on context and industry standards, documenting assumptions in the spec. Only critical ambiguities become [NEEDS CLARIFICATION] markers, limited to three, which are presented to the user as multiple-choice questions.

Does speckit-specify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory. It reads .specify/init-options.json for numbering mode, resolves the spec-template, and persists the feature path to .specify/feature.json for downstream commands.

Can speckit-specify create a git branch automatically?▼

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

What happens if the generated spec fails validation?▼

The command checks the spec against a quality checklist covering content quality, requirement completeness, and feature readiness. It updates the spec and re-validates up to three times, documenting any remaining issues in the checklist notes.