speckit-specify

Generates feature specs and creates Git branches from natural language descriptions.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-specify-refactory-lang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-specify-refactory-lang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of detailed feature specifications from simple natural language descriptions, streamlining the initial stages of product development.

Core Features & Use Cases

  • Automated Spec Generation: Creates user stories, functional requirements, and acceptance criteria.
  • Branch Management: Automatically generates a descriptive branch name and creates the feature branch.
  • Use Case: When a product manager describes a new feature like "Implement user authentication with OAuth2", this Skill generates a spec.md file, a checklist, and a new Git branch ready for development.

Quick Start

Use the speckit-specify skill to create a new feature specification for adding user authentication.

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 parsing natural language descriptions to create user stories, functional requirements, and acceptance criteria. This automates requirements gathering by producing a structured spec.md file and checklist for development.

Can I automatically create a Git branch when starting feature development?

Yes, Git branch creation is automated during feature specification generation. The workflow derives a descriptive branch name from the natural language input and executes bash scripts to initialize the branch for spec-driven development.

Do I need a specific project structure to use spec-driven development workflows?

Spec-driven development workflows require a project containing a `.specify/` directory structure. This environment must include associated bash scripts to properly handle branch generation and spec file creation.

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

Writing user stories and acceptance criteria is best handled by inputting a simple feature description. The system automatically structures the requirements into a comprehensive specification document, streamlining the initial product management phase.

Does this requirements gathering workflow integrate with my existing Git workflow?

Yes, the workflow integrates directly with your Git workflow by generating a descriptive branch name and creating the feature branch automatically. This ensures specification generation aligns with your existing version control practices.

What are the limitations of generating feature specs from natural language?

Generating feature specs from natural language relies on the presence of a `.specify/` directory and associated bash scripts. Without this specific project structure, the automatic spec file generation and branch creation cannot execute.