speckit-specify

Transform natural language feature descriptions into structured specifications with acceptance criteria.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-specify-chaimt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/speckit-specify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-specify-chaimt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms a natural language feature description into a complete, plan-ready specification.

Core Features & Use Cases

  • Automates extraction of key concepts (actors, actions, data, constraints) from a user prompt.
  • Guides clarification only when needed and limits prompts to critical decisions.
  • Produces a complete feature spec with user scenarios, functional requirements, acceptance criteria, and testable scenarios.
  • Validates spec quality with an integrated checklist and iterative refinement until ready for planning.

Quick Start

Provide a natural language feature description to generate a speckit.specify-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 a feature idea into a structured specification?

Transform a natural language feature idea into a structured specification by extracting actors, actions, data, and constraints to generate user stories, functional requirements, and acceptance criteria.

What is the best way to write functional requirements from a feature description?

The best way to write functional requirements is automating extraction of key concepts from a natural language description to capture user scenarios, constraints, and testable success criteria.

Can I generate user stories and acceptance criteria from a single descriptive prompt?

Yes, you can generate user stories and acceptance criteria from a single descriptive prompt by applying specification workflows that capture requirements and validate spec quality iteratively.

Does this specification approach work for product discovery and validation workflows?

This specification approach works directly for product discovery and validation workflows by applying an integrated quality checklist to refine assumptions and testable scenarios until plan-ready.

How do you validate feature specification quality before planning begins?

Validate feature specification quality before planning by applying an integrated checklist that iteratively refines assumptions, constraints, and success criteria until the spec is complete.

What is needed to start drafting a plan-ready feature specification?

To start drafting a plan-ready feature specification, you only need a natural language feature description to automate concept extraction and guide critical clarification decisions.