speckit-specify

Generate formal feature specifications from natural language descriptions.

Updated Mar 29, 2026

Search Tags:#planning #templates #specification #requirements #validation #feature #natural-language

Ready to run

npx skills add https://github.com/iltan987/jetadisyon --skill speckit-specify-iltan987

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert informal feature ideas and user stories into a fully structured specification document, reducing ambiguity and speeding up the planning process.

Core Features & Use Cases

Auto-generates a feature outline from a natural language description and enforces a structured template with sections for user scenarios, acceptance criteria, testing, and validation.
Validates quality with an integrated outline, clarifications prompts (up to 3), and a plan for artifact creation, storage, and downstream consumption.
Supports end-to-end planning by producing a SPEC_FILE, a feature directory under specs/, and a reusable quality checklist for planning readiness.

Quick Start

Describe your feature in natural language to generate a complete, plan-ready specification.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema

How do I turn natural language descriptions into structured feature specifications?▼

To turn natural language descriptions into structured feature specifications, input your feature idea to auto-generate a plan-ready document with user scenarios, acceptance criteria, and testing definitions. It applies a structured template to reduce ambiguity and speed up planning.

What is the best way to generate acceptance criteria and user scenarios for a new feature?▼

Generating acceptance criteria and user scenarios involves applying a structured specification template to your natural language input. This process auto-generates a formal feature outline, enforces validation quality, and produces a reusable checklist for planning readiness.

Do I need a spec-kit project with a .specify directory to create feature specifications?▼

Yes, you need a spec-kit project with a .specify directory to create and store formal feature specifications. This directory structure is required to generate the SPEC_FILE, validate quality, and store artifacts for downstream consumption.

How does an automated specification outline handle validation and clarifications?▼

An automated specification outline handles validation by enforcing a structured template and prompting up to three clarifications. It ensures quality by defining measurable success criteria and generating a plan for artifact creation and downstream consumption.

Can I update existing requirements documents using natural language input?▼

Yes, you can update existing feature specifications using natural language input. The process reads your current spec-kit project, applies your new descriptions to the existing structure, and regenerates the formal specification with updated validation.

What limitations exist when auto-generating feature specifications from informal descriptions?▼

Limitations of auto-generating feature specifications include a strict dependency on the .specify directory for artifact storage and a maximum of three clarification prompts to resolve natural language ambiguity before generating the final document.