speckit-clarify

Detects and resolves specification ambiguities through structured coverage-based questioning before planning.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-clarify-alex-jordan547
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/speckit-clarify
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-clarify-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and ambiguous terms that cause rework during implementation. This Skill systematically scans a spec-kit feature specification for gaps and resolves them through targeted questions before planning begins. ## Core Features & Use Cases - Coverage-Based Ambiguity Scan: Evaluates the spec across a taxonomy of categories including functional scope, data model, UX flow, non-functional attributes, integrations, edge cases, and terminology. - Prioritized Interactive Questioning: Asks up to 5 high-impact questions one at a time, each with a recommended multiple-choice option or suggested short answer based on best practices. - Incremental Spec Updates: Records each accepted answer in a ## Clarifications session section and applies it to the relevant spec sections, saving after every integration. - Use Case: Before running /speckit.plan on a new feature spec, run this Skill to resolve questions like authentication strategy, data retention limits, or error handling behavior, so the plan is built on confirmed decisions. ## Quick Start Ask the agent to clarify the current feature specification with speckit-clarify before creating the implementation plan.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguous requirements in a spec-kit specification?▼

Run the clarify workflow before planning. It scans the feature spec across categories like functional scope, data model, and edge cases, then asks up to 5 prioritized questions and records each accepted answer in a Clarifications section of the spec file.

When should I run specification clarification in a spec-driven workflow?▼

Run it after creating the feature specification and before invoking the planning command. Skipping clarification increases downstream rework risk, though you may proceed explicitly for exploratory spikes.

Does speckit-clarify work without a spec-kit project structure?▼

No. It requires a spec-kit project with a .specify directory and runs check-prerequisites.sh to locate the feature spec. If the spec file is missing, it instructs you to run the specify command first.

How many clarification questions does the workflow ask?▼

It asks a maximum of 5 questions per session, selected by impact and uncertainty across unresolved categories. Each question offers a recommended multiple-choice option or a suggested short answer of five words or fewer.

What happens if no ambiguities are found in the specification?▼

The workflow reports that no critical ambiguities were detected, outputs a compact coverage summary showing all categories as clear, and suggests proceeding directly to the planning phase.