speckit-specify

Generate a ready-to-plan specification from a natural-language feature description.

120|25|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-specify-dceoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-specify
Command: npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-specify-dceoy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Product teams often struggle to turn a natural-language feature idea into a concrete specification that can be handed to planning and execution.

Core Features & Use Cases

  • Generate a complete spec from a natural-language description that includes all mandatory sections.
  • Validate the spec against templates, assumptions, and acceptance criteria, and produce a planning checklist.
  • Initialize a new spec branch and prepare traceable artifacts for review and planning.

Quick Start

Provide a natural-language feature description and the skill will generate a ready-to-plan spec, initialize a new spec branch, and create a validation checklist.

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 complete specification?

To turn a natural-language feature description into a complete specification, provide your idea to generate a ready-to-plan spec file that includes mandatory sections, drafted assumptions, and testable acceptance criteria.

What is the best way to generate feature specs and a validation checklist for planning?

The best way to generate feature specs and a validation checklist is using Spec Kit workflows, which transform ideas into technology-agnostic spec files and produce traceable artifacts with testable acceptance criteria for review.

How do I draft assumptions and acceptance criteria for a feature spec?

You draft assumptions and acceptance criteria for a feature spec by processing the feature description through a specification generator, which automatically fills mandatory sections and creates a technology-agnostic validation checklist.

Can I initialize a new spec branch and prepare traceable artifacts for review?

Yes, you can initialize a new spec branch and prepare traceable artifacts for review, as the specification process automatically generates a spec file, requirements checklist, and testable acceptance criteria for planning.

Does the generated feature specification work with any technology stack?

Yes, the generated feature specification is technology-agnostic, meaning the resulting spec file, requirements checklist, and testable acceptance criteria are designed to be easy to verify across any technology stack.