speckit-specify

Generate structured specification documents and development branch plans from natural-language feature descriptions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jimmyfcis/newfantasy --skill speckit-specify-jimmyfcis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/jimmyfcis/newfantasy/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/jimmyfcis/newfantasy --skill speckit-specify-jimmyfcis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured specification from a natural-language feature description, enabling consistent planning and documentation.

Core Features & Use Cases

  • Generate a complete spec document with user scenarios, requirements, dependencies, and acceptance criteria from plain-language input.
  • Produce a branch plan and template-aligned spec file that can be handed to product and engineering teams.
  • Validate quality through a built-in checklist and optional post-spec hooks for downstream tooling.

Quick Start

Describe the feature you want to specify and run the speckit.specify command to generate a ready-to-plan 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 natural language feature descriptions into structured specification documents?▼

To turn natural language into a structured specification, describe your feature and the skill generates a spec document covering user scenarios, requirements, acceptance criteria, and validation steps from plain-language input.

What is the best way to generate user scenarios and acceptance criteria from plain text?▼

Generating user scenarios and acceptance criteria from plain text involves applying project templates and a defined frontmatter spec to parse feature descriptions into measurable success criteria and a quality checklist.

Can I create a development branch plan automatically from a feature spec?▼

Yes, you can create a development branch plan automatically from a feature spec, as the process produces a template-aligned spec file and a branch plan ready to hand to product and engineering teams.

Does the specification process include validation for functional requirements?▼

Yes, specification validation for functional requirements is included through a built-in quality checklist that verifies dependencies, measurable success criteria, and optional post-spec hooks for downstream tooling.

How do I ensure consistent feature documentation across product and engineering teams?▼

Ensuring consistent feature documentation across teams requires applying defined project templates and frontmatter specs, transforming plain-language input into standardized specification documents and branch plans.