speckit-clarify

Identifies underspecified areas in feature specs and records targeted clarification answers.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-clarify-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-clarify-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguities, missing decisions, and vague requirements that cause rework during planning and implementation. This Skill systematically detects those gaps and resolves them through structured questioning before development begins. ## Core Features & Use Cases - Ambiguity Scanning: Performs a structured coverage scan across taxonomy categories like functional scope, data model, non-functional requirements, and edge cases, marking each as Clear, Partial, or Missing. - Interactive Clarification Loop: Asks up to 5 high-impact questions one at a time, offering recommended multiple-choice options or suggested short answers grounded in project context files. - Incremental Spec Updates: Writes each accepted answer back into the spec file under a Clarifications session heading and updates the relevant requirement sections atomically. - Use Case: Before running implementation planning on a new ordering feature in a .NET e-commerce project, run this Skill to resolve open questions about concurrency handling, data retention, and acceptance criteria so the plan is built on firm decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to find and resolve ambiguities before planning.

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

Run the clarification workflow after creating a spec with speckit-specify. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the answers directly into the spec file.

How many clarification questions does the spec-kit clarify workflow ask?▼

The workflow asks a maximum of 5 questions per session, selected by impact and uncertainty. Each question is either multiple-choice with a recommended option or a short answer constrained to five words or fewer.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory and an active feature spec created by speckit-specify. It runs check-prerequisites scripts to locate the feature directory and spec file, and aborts if they are missing.

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

Run clarification before speckit-plan whenever the spec contains unresolved decisions or vague requirements. Skipping it is allowed for exploratory spikes, but the workflow warns that downstream rework risk increases significantly.

What happens to clarification answers after I respond?▼

Each accepted answer is appended as a bullet under a Clarifications session heading dated by day, then applied to the relevant spec section such as Functional Requirements or Success Criteria. The spec file is saved after each integration.