speckit-specify

Convert vague feature ideas into structured specifications with acceptance criteria.

Updated May 20, 2026

Search Tags:#planning #specification #requirements #feature #quality-checks #clarifications

Ready to run

npx skills add https://github.com/igmo71/Myrmex --skill speckit-specify-igmo71

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/igmo71/Myrmex/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/igmo71/Myrmex --skill speckit-specify-igmo71

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps product teams convert informal feature ideas into precise, actionable specifications that guide planning and execution.

Core Features & Use Cases

Generates a structured spec from natural language descriptions.
Validates completeness with a quality checklist and prompts for clarifications when needed.
Produces a ready-to-plan spec document and metadata for downstream planning tools.

Quick Start

Describe your feature in natural language to generate a complete spec ready for planning.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema

How do I turn a vague feature idea into a structured specification?▼

You can generate a structured specification by providing a natural language description of your feature request, which produces a ready-to-plan spec document with defined sections, acceptance criteria, and testing considerations.

What is the best way to write product specifications with clear acceptance criteria?▼

Writing product specifications with clear acceptance criteria involves using a tool that applies a quality checklist to validate completeness and prompts for clarifications, ensuring actionable success criteria are met.

How do I check if my feature requirements are complete before planning?▼

To check if feature requirements are complete, you use a validation process that applies a quality checklist to your spec, prompting for necessary clarifications to ensure scope and acceptance criteria are fully defined.

Can I generate specs for both design and engineering teams from the same feature request?▼

Yes, you can generate specs for design and engineering teams from the same feature request because the specification process covers scope, acceptance criteria, and testing considerations applicable across product, design, and engineering teams.

What do I need to provide to generate a ready-to-plan spec document?▼

You only need to provide a natural language description of your feature idea to generate a ready-to-plan spec document, which includes structured sections and metadata for downstream planning tools.

Why does my specification need prompts for clarifications?▼

Specifications need prompts for clarifications to validate completeness, ensuring vague aspects of a feature idea are resolved into precise, actionable requirements with defined scope and actionable success criteria before planning begins.