speckit-specify

Generate a formal spec.md from a natural language feature description.

Updated May 28, 2026
One-click install
npx skills add https://github.com/bdunnette/reaper --skill speckit-specify-bdunnette
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/bdunnette/reaper/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/bdunnette/reaper --skill speckit-specify-bdunnette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-Specify automates turning a natural language feature description into a fully structured spec ready for planning, with built-in pre-execution checks, memory constitution loading, and quality validation.

Core Features & Use Cases

  • Natural language to spec: Converts user prompts into a complete Feature Specification with sections and checklists.
  • Template-driven planning: Resolves spec-template, creates spec.md under specs/, and writes feature.json for downstream steps.
  • Quality validation: Generates a spec quality checklist and supports iterative clarifications and re-validation.
  • Use Case: A product manager describes a feature like "Add in-app dark mode with per-device theming" and Speckit-Specify produces a ready-to-plan spec file and a validation checklist.

Quick Start

Provide a feature description after the /speckit-specify command to begin generating the 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 natural language feature description into a formal specification?

To turn a natural language feature description into a formal specification, provide your prompt to generate a spec.md file with structured sections, loaded templates, and a quality checklist under the specs/ directory.

What is the best way to automate feature spec creation for project planning?

Automating feature spec creation involves using template-driven tooling to parse prompts, apply a three-section description structure, and output a completed spec file path alongside a feature.json file for downstream planning steps.

How does quality validation work when generating a feature specification?

Quality validation for a feature specification works by generating a spec quality checklist, performing validation against defined criteria, and supporting iterative clarifications and re-validation to ensure completeness.

Do I need specific tooling to generate a spec directory and spec.md file?

Yes, generating a spec directory and spec.md file requires projects using the spec-kit tooling, as the process scans for extension hooks and loads memory constitution to produce the final specification.

Can I use a template to enforce structure when writing feature specs?

Yes, you can use a template to enforce structure by resolving spec-templates that automatically apply a mandated three-section description structure and generate a ready-to-plan specification document.

Why does my specification generation fail during pre-execution checks?

Specification generation may fail during pre-execution checks if the environment lacks proper spec-kit tooling setup, missing extension hooks, or unmet memory constitution loading requirements needed to validate the spec.