speckit-specify

Generate spec.md files and requirements checklists from natural language descriptions.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-specify-kamalsroor1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/kamalsroor1/nest-scaffolding-crud-manager/tree/main/.agent/skills/speckit-specify
Command: npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-specify-kamalsroor1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts informal, natural-language feature descriptions into a structured, testable product specification so teams avoid ambiguous requirements and reduce planning delays.

Core Features & Use Cases

  • Template-driven spec creation: Generates a spec.md inside a new feature directory using .specify/templates/spec-template.md and records the path in .specify/feature.json.
  • Pre/post extension hook support: Detects and reports optional or mandatory hooks from .specify/extensions.yml and surfaces commands or automatic executions without evaluating hook conditions.
  • Quality validation and checklists: Produces a requirements checklist, validates the spec against quality criteria, iterates fixes up to three times, and lists remaining clarifications via up to three [NEEDS CLARIFICATION] questions.
  • Real-world example: Product managers can turn a short product idea into a ready spec folder (specs/003-new-checkout) with acceptance criteria and a validation checklist for planning.

Quick Start

Run the speckit-specify workflow with a clear feature description to create a spec.md and a quality checklist in the specs/ directory.

Frequently Asked Questions about speckit-specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a natural language feature description into a structured product spec?

To turn a natural language feature description into a structured product spec, provide the text to the workflow which generates a formal spec.md file and a requirements checklist inside a designated feature directory.

How does automated spec writing handle quality validation and missing requirements?

Automated spec writing validates generated files against quality criteria, iterates corrections up to three times, and lists remaining ambiguities using up to three [NEEDS CLARIFICATION] questions for unresolved requirements.

Can I use custom templates and extension hooks when generating feature specifications?

You can use custom templates from .specify/templates/ and configure optional or mandatory extension hooks via .specify/extensions.yml, which the system detects and reports during feature spec generation.

What is the best way to organize feature spec files for engineering planning?

The best way to organize feature spec files is within a specs/ directory structure, creating individual folders like specs/003-new-checkout that contain the spec.md, acceptance criteria, and validation checklists.

Does spec generation require manual folder creation before writing the spec.md file?

Spec generation does not require manual folder creation; it automatically creates the specs/<prefix>-<short-name> directory, writes the spec.md file, and records the path in .specify/feature.json.

Why do my informal product requirements cause planning delays and ambiguous specs?

Informal product requirements cause planning delays due to ambiguity, which this specification process solves by converting natural language descriptions into testable, structured product specifications with clear acceptance criteria.