speckit.specify

Convert natural language prompts into structured feature specification documents with validation checklists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts natural language feature prompts into structured, ready-to-plan specifications, reducing ambiguity and speeding up early-stage product discovery.

Core Features & Use Cases

  • Automatically generate a complete feature specification with sections like problem, goals, requirements, success criteria, and assumptions.
  • Validate spec quality via an integrated checklist and produce an actionable SPEC_FILE saved in the designated template.
  • Use for brainstorming, planning, and documentation in product development across teams.

Quick Start

Describe your feature in plain language and let speckit.specify produce a complete spec ready for review.

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 feature specification from a natural language prompt?▼

To generate a feature specification, you describe a feature in plain language and the tool converts the prompt into a structured spec document, handling product discovery and documentation workflows.

What sections are included in a structured feature specification?▼

A structured feature specification includes sections for the problem, goals, requirements, success criteria, and assumptions to ensure comprehensive product planning and reduce ambiguity.

How do I validate requirements and spec quality before saving?▼

You validate requirements and spec quality using an integrated validation checklist, ensuring all mandatory frontmatter and required sections are present before saving to the designated SPEC_FILE path.

Can I use plain language prompts for product planning and discovery?▼

Yes, you can use plain language prompts for product planning and discovery; the tool processes natural language feature descriptions to produce consistent, structured specs ready for review.

What is the best way to turn brainstorming ideas into ready-to-plan specifications?▼

The best way to turn brainstorming ideas into ready-to-plan specifications is to input the raw feature descriptions, letting the system automatically apply templates and user-driven clarifications to produce a validated spec.

Does this approach to specification creation work for cross-functional team documentation?▼

Yes, this specification creation approach works for cross-functional team documentation by standardizing feature specs with consistent problem, goal, and requirement sections across product development teams.