speckit-specify

Generate structured feature specifications from natural language inputs.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/kimen-dev/kimen --skill speckit-specify-kimen-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/kimen-dev/kimen/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/kimen-dev/kimen --skill speckit-specify-kimen-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inconsistency and ambiguity often found in early-stage feature definitions by enforcing a structured, testable, and quality-validated specification process.

Core Features & Use Cases

  • Automated Spec Generation: Transforms natural language descriptions into structured, professional specification documents.
  • Quality Validation: Automatically generates and runs a quality checklist to ensure requirements are testable, measurable, and free of implementation bias.
  • Use Case: A product manager provides a rough idea for a new user authentication flow, and the skill generates a complete spec with functional requirements, success criteria, and user scenarios, while flagging missing information for clarification.

Quick Start

Invoke the speckit-specify skill followed by a natural language description of the feature you wish to define.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate structured feature specifications from natural language?

Generate structured feature specifications by inputting natural language descriptions, which are transformed into professional, testable requirement documents with functional criteria and user scenarios.

How does automated quality validation work for product requirements?

Automated quality validation for product requirements works by generating a checklist to ensure specifications are testable, measurable, and free of implementation bias, while flagging missing information.

What is the best way to standardize early-stage feature definitions?

The best way to standardize early-stage feature definitions is enforcing a structured, quality-validated specification process that transforms rough ideas into clear, testable documentation.

Can I create testable user scenarios from a rough product idea?

Yes, you can create testable user scenarios from a rough product idea by processing the natural language input to generate complete specifications with functional requirements and success criteria.

Does automated spec generation work for agile software development lifecycles?

Yes, automated spec generation works for agile software development lifecycles by producing technology-agnostic, user-focused documentation prepared for planning and validated against quality checklists.

Why are my feature specifications missing implementation details?

Feature specifications may miss implementation details because the process enforces technology-agnostic, user-focused documentation, intentionally removing implementation bias and flagging gaps for clarification.