speckit-clarify

Identify and resolve ambiguities in feature specifications through targeted clarification questions.

5|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-clarify-theonlytruebigmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/theonlytruebigmac/n-central-rest-api-mcp/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-clarify-theonlytruebigmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and unresolved edge cases that cause rework during planning and implementation. This Skill systematically detects underspecified areas and encodes the answers directly back into the spec file. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended option or suggested answer to speed up decisions. - Incremental Spec Updates: Writes each accepted answer into a ## Clarifications section and updates the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running implementation planning on a new feature spec, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so downstream tasks are built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to find and resolve its ambiguities.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguities in a feature specification?▼

Run the clarify workflow on your spec file, which scans it against a coverage taxonomy and asks up to 5 targeted questions. Each accepted answer is written back into the spec under a Clarifications section and applied to the relevant requirement sections.

What is the spec-kit clarify command used for?▼

The clarify command reduces underspecified areas in a feature spec before planning begins. It prioritizes questions by impact and uncertainty, covering functional scope, data models, non-functional requirements, and edge cases.

Does spec-kit clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts and the feature spec. It runs check-prerequisites.sh to locate FEATURE_DIR and FEATURE_SPEC, and aborts if the spec file is missing.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Each must be answerable with a multiple-choice selection or a short answer of five words or fewer, and retries for the same question do not count against the limit.

When should I run clarification versus going straight to planning?▼

Run clarification before the plan step whenever the spec contains vague terms, unresolved decisions, or missing acceptance criteria. Skipping it is allowed for exploratory spikes, but it increases downstream rework risk.