speckit-specify

Translate natural language feature descriptions into testable specification documents.

9|4|Updated May 13, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-specify-opsmill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-specify-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-specify helps product teams and AI agents turn vague feature ideas into precise, testable specifications by automatically generating structured spec content from natural language prompts.

Core Features & Use Cases

  • Parses natural language feature descriptions
  • Generates concise feature short-name and a spec.md from templates
  • Creates and configures spec directories, checklists, and validation artifacts
  • Supports extension hooks and after-specify hooks for customization

Quick Start

Describe the feature you want to specify in plain language to generate a complete spec draft.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate a testable specification from a natural language feature description?

To generate a testable specification from a natural language feature description, input your plain text prompt to automatically create a structured spec directory, populate a spec.md from a template, and validate it through a quality checklist.

What is the best way to structure feature specs for product teams using plain text?

Structuring feature specs from plain text involves parsing the natural language input to generate a concise short-name, creating a dedicated specs/ directory, and loading a template to produce a plan-ready specification document.

Can I customize the specification workflow with extension hooks after generating a spec?

Yes, you can customize the specification workflow by utilizing supported extension hooks and after-specify hooks, allowing you to tailor the artifact generation and validation process to fit your specific product team requirements.

How does checklist validation ensure a plan-ready specification document?

Checklist validation ensures a plan-ready specification document by performing iterative quality checks on the generated spec.md, enforcing a structured artifact workflow that validates content readiness until all specification criteria are met.

Does this specification tool require any dependencies to create spec directories?

No dependencies are required to create spec directories and generate feature specifications, as the tool operates independently to parse natural language, load templates, and execute validation workflows without external module prerequisites.