speckit-specify

Name: speckit-specify
Availability: InStock
Author: Numu

Convert natural-language feature ideas into structured specifications with scenarios and success criteria.

2|Updated Jan 6, 2026

Search Tags:#checklist #specification #requirements #clarification #feature planning #success criteria #user scenarios

Ready to run

npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-specify-numu-io

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-specify-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns rough feature ideas into clear, testable specifications so teams can align on scope, outcomes, and success criteria before planning work.

Core Features & Use Cases

Spec Creation: Converts a natural-language feature request into a structured specification with user scenarios, functional requirements, assumptions, and measurable success criteria.
Scope Clarification: Identifies the few critical ambiguities that would materially affect the feature and surfaces them as focused questions.
Readiness Validation: Checks the draft for completeness, testability, and planning readiness, then produces a checklist for review.
Use Case: A product manager describes a new checkout flow, and the Skill produces a complete spec that engineering and design can use as the starting point for planning.

Quick Start

Ask the speckit-specify skill to turn your feature idea into a complete, testable specification 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 feature idea into a structured specification?▼

To turn a feature idea into a structured specification, provide a natural-language request and the system converts it into user scenarios, functional requirements, and success criteria for planning.

What is the best way to define user scenarios and functional requirements for new features?▼

Defining user scenarios and functional requirements involves converting a natural-language feature request into a structured specification that includes assumptions and measurable success criteria.

How do I identify scope ambiguities when planning a new feature?▼

Identifying scope ambiguities is handled by surfacing the few critical scope clarifications that would materially affect the feature, presenting them as focused questions for review.

How do I validate planning readiness for a feature specification?▼

Validating planning readiness checks the draft specification for completeness and testability, then produces a review checklist to ensure the feature is ready for engineering.

Can I create testable specifications from a rough product request without losing repository conventions?▼

Creating testable specifications from rough requests preserves repository conventions while applying bounded clarification prompts to generate structured specs with measurable success criteria.

Does feature specification generation work for updating existing features?▼

Feature specification generation works for both new and updated features, converting natural-language ideas into structured specifications with bounded clarification prompts and planning checklists.