speckit-specify

Name: speckit-specify
Availability: InStock
Author: Kami

Convert natural language feature descriptions into structured specifications with success criteria.

Updated May 18, 2026

Search Tags:#scoping #specification #requirements #validation #feature planning #product discovery

Ready to run

npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-specify-kamijeong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-specify-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a natural-language feature idea into a structured, testable specification so planning can begin without ambiguity or guesswork.

Core Features & Use Cases

Feature Scoping: Captures the goal, user needs, and boundaries of a requested feature.
Spec Drafting: Produces a complete spec with requirements, success criteria, assumptions, and entities when relevant.
Quality Validation: Checks the spec for missing details, unclear requirements, and readiness issues before planning.
Use Case: A product owner can describe a lesson, workflow, or app feature in plain language and get a planning-ready spec that the team can review.

Quick Start

Ask the skill to create a spec for your feature idea and include the target user, goal, and main outcome you want.

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 for planning?▼

To turn a feature idea into a structured specification, provide a natural language description with the target user, goal, and main outcome to generate a planning-ready spec with clear requirements and success criteria.

What is feature scoping and how does it validate requirements?▼

Feature scoping captures the goal, user needs, and boundaries of a requested feature. It validates requirements by checking the drafted spec for missing details, unclear requirements, and readiness issues before downstream planning.

Can I draft a feature spec for workflow updates and lesson requests?▼

Yes, you can draft a feature spec for workflow updates and lesson requests. This applies to any scoped initiative needing clear requirements, capturing user scenarios, functional requirements, and measurable success criteria.

What's the best way to write measurable success criteria for product changes?▼

The best way to write measurable success criteria for product changes is to convert plain language descriptions into a structured specification, ensuring all assumptions and functional requirements are validated for readiness.

Do I need to provide user scenarios to generate a planning-ready spec?▼

Yes, providing user scenarios is required to generate a planning-ready spec. The specification process validates these scenarios alongside functional requirements and assumptions to ensure downstream planning workflows proceed without ambiguity.