speckit-specify

Generate template-based feature specs and create feature branches from natural language descriptions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts informal, natural-language feature descriptions into structured, planning-ready specifications and automates creating the corresponding feature branch so product and engineering teams can move faster and reduce misunderstandings.

Core Features & Use Cases

  • Branch creation: Generates a concise short-name and invokes the project script to create and check out a new feature branch, returning machine-readable JSON with branch and spec paths.
  • Template-driven spec authoring: Fills the .specify/templates/spec-template.md structure with actors, scenarios, functional requirements, success criteria, entities, and documented assumptions.
  • Quality validation and checklists: Produces FEATURE_DIR/checklists/requirements.md, runs iterative validation against the checklist, surfaces up to three critical clarifying questions, and updates the spec until it passes checks or reports outstanding issues.
  • Extension hook support: Detects and lists or executes pre- and post-specify hooks defined in .specify/extensions.yml, handling optional and mandatory hooks according to configuration.
  • Use case: A product manager types a brief feature description into chat and receives a ready-to-plan spec file, a quality checklist, and a newly created branch for engineering work.

Quick Start

Invoke the skill with a concise feature description such as: /speckit.specify Add user authentication to generate the feature spec, validation checklist, and new branch.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I convert a natural language feature description into a structured specification?

Feature specifications are generated by parsing natural language descriptions and populating a template structure with actors, scenarios, and functional requirements. This process outputs ready-to-plan spec files and a JSON checklist under the .specify workspace.

How do I automatically create a feature branch when writing a new feature spec?

Automatic branch creation is handled by generating a short-name from the feature description and invoking the project script to check out a new branch. The process returns machine-readable JSON containing the branch name and the corresponding spec path.

What is the best way to validate feature specification quality iteratively?

Iterative quality validation is performed by generating a requirements checklist and running checks against the specification. The system surfaces up to three critical clarifying questions and updates the spec until it passes all checks or reports outstanding issues.

Can I execute pre and post hooks during the feature specification workflow?

Extension hooks are supported by detecting and listing pre- and post-specify hooks defined in the extensions.yml configuration file. The workflow executes both optional and mandatory hooks according to the project's specific configuration settings.

Do I need a specific project layout to generate template-based spec files?

The spec-kit layout is required to generate template-based spec files, ensuring output follows the spec-template.md structure. Files and validation checklists are written directly under the .specify workspace directory within the project.

What should a feature specification template include for engineering planning?

A feature specification template should include actors, scenarios, functional requirements, success criteria, entities, and documented assumptions. This structure ensures engineering teams receive comprehensive planning-ready documents from initial feature ideas.