speckit-specify

Convert natural language feature descriptions into user stories, requirements, and acceptance criteria.

Updated Aug 23, 2026

Search Tags:#workflow #planning #specification #requirements #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-specify-leonardomoraisf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-specify-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Specify converts natural language feature ideas into precise, formal specifications to reduce ambiguity and rework during planning.

Core Features & Use Cases

Specification generation: outputs user stories, functional requirements, and acceptance criteria from a description.
Spec maintenance: creates or updates spec.md in the project using a consistent template.
Guided workflow: follows a spec-driven development methodology with outline, checks, and validation steps.
Scope guidance: assists starting new features or refining existing requirements for clearer scope.

Quick Start

Provide a natural language feature description after /speckit.specify to generate a complete Spec.md with user stories, functional 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 turn natural language feature descriptions into formal specifications?▼

To turn natural language feature descriptions into formal specifications, provide your text input to generate user stories, functional requirements, acceptance criteria, and a quality checklist for plan-ready outputs.

What is the best way to write user stories and acceptance criteria from a rough feature idea?▼

Writing user stories and acceptance criteria from a rough feature idea involves transforming the text into a spec.md file using a guided, spec-driven development workflow with validation steps.

Can I use this to refine existing requirements for clearer scope alignment?▼

Yes, you can refine existing requirements for clearer scope alignment by processing your current descriptions to output structured functional requirements and validate stakeholder expectations.

Does this approach maintain a consistent specification template across a project?▼

Yes, this specification approach maintains a consistent template by creating or updating a spec.md file in the project, ensuring all feature requirements follow a standardized format.

Why should I use a spec-driven development methodology for planning new features?▼

You should use a spec-driven development methodology for planning new features to reduce ambiguity and rework by generating formal, plan-ready specifications with validation checks before implementation.