speckit-specify

Name: speckit-specify
Availability: InStock
Author: tykhoncode

Convert natural-language feature ideas into validated, testable specifications.

Updated May 3, 2026

Search Tags:#feature specification #requirements engineering #product planning #quality validation #extension hooks #natural language to spec

Ready to run

npx skills add https://github.com/tykhoncode/dicekit --skill speckit-specify-tykhoncode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/tykhoncode/dicekit/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/tykhoncode/dicekit --skill speckit-specify-tykhoncode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert a natural-language feature idea into a structured, stakeholder-friendly specification that can be used for planning and clarification, reducing ambiguity before implementation starts.

Core Features & Use Cases

Generates a feature spec directory and spec.md from a short, user-provided description.
Supports project-level extension hooks to run optional or mandatory pre-specification steps.
Produces a testable, technology-agnostic spec with user scenarios, functional requirements, and measurable success criteria.
Validates spec quality via an automatically generated checklist and iteratively improves the output up to three times.

Quick Start

Create a new feature spec from your description by running: specify your desired feature details after /speckit-specify.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema

How do I convert a natural language feature idea into a structured specification?▼

To convert a natural language feature idea into a structured specification, you provide a short description and the system generates a testable spec with user scenarios, functional requirements, and success criteria. It creates a feature spec directory and spec.md while validating quality through an automated checklist.

What is requirements engineering for product planning and how does it reduce ambiguity?▼

Requirements engineering for product planning translates stakeholder needs into measurable success criteria and functional requirements. This process reduces ambiguity before implementation starts by enforcing quality validation and generating required spec sections from a template.

How do I generate testable functional requirements from a short product description?▼

You generate testable functional requirements by processing your short product description through a specification template. The system iteratively improves the output up to three times using an automatically generated checklist to ensure minimal ambiguity and measurable success criteria.

Can I run pre-specification steps before generating a feature spec?▼

Yes, you can run pre-specification steps by utilizing project-level extension hooks. The system honors before_specify extension hooks to execute optional or mandatory pre-specification actions before generating the feature directory and spec.md file.

Does the feature specification process support configurable directory numbering?▼

Yes, the feature specification process supports configurable directory numbering. When generating the feature spec directory and spec.md file, the system honors configurable directory numbering settings alongside before_specify extension hooks.

How many times will the system iteratively improve a generated specification?▼

The system iteratively improves a generated specification up to three times. It validates spec quality via an automatically generated checklist after converting your natural-language feature idea into a complete, validated, testable specification.