speckit-specify

Generate spec.md files with user stories, requirements, and acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates natural language feature ideas into precise, implementable specifications by generating a spec.md with user stories, functional requirements, and acceptance criteria, streamlining the move from ideation to planning.

Core Features & Use Cases

  • Scans the project for available skills (typically under .agent/skills or equivalent) and follows relevant SKILL.md instructions before drafting a new spec.
  • Generates a complete spec.md with sections for user stories, functional requirements, acceptance criteria, and optional checklists based on the provided feature description.
  • Loads and adheres to a standard template (spec-template.md) to ensure consistency across specs.
  • Performs quality validation with a structured checklist and iterative refinement when clarifications are needed.
  • Produces a ready-to-use branch and file layout for planning and development.

Quick Start

Describe the feature briefly and run speckit-specify to generate a complete spec.md with user stories, 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 concrete user stories and acceptance criteria?

To turn natural language into user stories and acceptance criteria, describe your feature idea and let the tool generate a structured spec.md. It automatically drafts functional requirements and validation workflows from your text input.

What is the best way to generate structured feature specifications for project planning?

The best way to generate feature specifications is to use an automated spec generator that applies a standard template. It produces a consistent spec.md with structured requirements and a quality checklist for planning.

Do I need a specific project directory structure to generate spec.md files automatically?

Yes, you need a project context that includes a .specify/ directory and a templates/spec-template.md file. The tool loads this template to ensure your generated spec.md maintains consistent formatting.

How does quality validation work when generating requirements and user stories?

Quality validation works by applying a structured checklist to the generated user stories and functional requirements. It performs iterative refinement when clarifications are needed to ensure the spec is implementable.

Can I refine existing requirement descriptions into ready feature specs?

Yes, you can refine existing requirements by providing the text for the new feature or refinement. The tool processes the description to produce a complete spec.md with acceptance criteria and a validation workflow.

What limitations exist when using templates for automated feature design and specification?

A key limitation is the strict dependency on the spec-template.md file for formatting consistency. If the template or the .specify/ directory is absent, the tool cannot produce the standardized spec.md output.