Verified:GitHub

speckit-specify

Generate spec.md files with user stories and acceptance criteria from natural language.

2|Updated Jan 29, 2026

Search Tags:#requirements #speckit #product-management #user-stories #acceptance-criteria #feature-specification #specify

Ready to run

npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-specify-pradeepmouli

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague feature ideas and requirements into formal, shareable specifications to accelerate planning, reduce ambiguity, and align cross-functional teams.

Core Features & Use Cases

Generate structured specs from natural language descriptions or user stories.
Produce sections such as user stories, functional requirements, acceptance criteria, and assumptions.
Support refinement of existing specifications to improve clarity and testability.

Quick Start

Describe the feature in natural language and Speckit Specify will generate a complete spec.md with user stories, requirements, and acceptance criteria.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema

How do I generate user stories and acceptance criteria from natural language feature descriptions?▼

Generating user stories and acceptance criteria from natural language feature descriptions is done by transforming the text into a formal spec.md. This file contains structured user scenarios, functional requirements, and testable validation steps for cross-functional team alignment.

What is the best way to turn vague product ideas into formal, testable specifications?▼

The best way to turn vague product ideas into formal, testable specifications is to process the descriptions into a structured spec.md. This document captures assumptions, functional requirements, and acceptance criteria to reduce ambiguity and accelerate planning.

Can I refine existing feature specifications to improve clarity and testability?▼

Yes, you can refine existing feature specifications to improve clarity and testability. The skill supports processing current requirements to produce updated user stories, functional requirements, and validation steps within a formal spec.md file.

Does generating feature specifications require a specific project structure?▼

Generating feature specifications requires a spec-kit project structure that uses a .specify directory. This environment setup allows the tool to automatically generate the complete spec.md file with all required sections for planning and review.

What sections are included when transforming feature descriptions into a spec.md file?▼

Transforming feature descriptions into a spec.md file produces sections for user scenarios, functional requirements, acceptance criteria, assumptions, and validation steps. These components ensure the formal specification is ready for immediate planning and cross-functional review.

How do I create a formal specification for cross-functional product, design, and engineering teams?▼

Creating a formal specification for cross-functional teams involves translating natural language inputs into a shared spec.md. The generated document provides aligned user stories and acceptance criteria to synchronize product, design, and engineering workflows.