speckit-specify

Generate a spec.md feature specification from natural language descriptions.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/raccioly/coach-gravity --skill speckit-specify-raccioly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/raccioly/coach-gravity/tree/main/.agent/skills/speckit-specify
Command: npx skills add https://github.com/raccioly/coach-gravity --skill speckit-specify-raccioly

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Create or update feature specifications from natural language descriptions to accelerate planning, reduce ambiguity, and align teams on the scope of work.

## Core Features & Use Cases

  • Generates a complete spec.md containing user stories, functional requirements, acceptance criteria, and assumptions from a plain-language feature description.
  • Creates and tracks a dedicated specification planning branch, coordinating with a spec-kit workflow and templates.
  • Includes an integrated quality-check process that produces a checklist and iterates until all items pass.

### Quick Start Provide a feature description to automatically generate a ready-to-plan spec.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate feature specifications from natural language descriptions?▼

Feature specifications are generated by providing a plain-language feature description to automatically create a spec.md containing user stories, functional requirements, and acceptance criteria.

What is the best way to write user stories and acceptance criteria for product planning?▼

Writing user stories and acceptance criteria is best handled by automating requirement refinement from a plain-language feature description to align teams on the scope of work.

Can I create a feature spec.md aligned with the spec-kit template automatically?▼

Yes, you can create a spec.md aligned with the spec-kit template automatically, which coordinates with a dedicated specification planning branch and standardizes your workflow.

How does the quality-check process work for feature specifications?▼

The quality-check process works by producing a checklist for the feature specification and iterating until all items pass, reducing ambiguity and aligning teams on scope.

Do I need any dependencies to define feature scope and functional requirements?▼

No dependencies are required to define feature scope and functional requirements. You simply provide the feature description to generate the ready-to-plan spec.md output.

What are the limitations of using natural language for requirement refinement?▼

Requirement refinement from natural language relies on the clarity of your input description to accurately generate functional requirements and assumptions without ambiguity.