speckit-clarify

Detects underspecified areas in feature specs and encodes clarification answers back into the spec file.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-clarify-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-clarify-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguous requirements, missing edge cases, and vague non-functional criteria that cause rework during planning and implementation. This Skill systematically scans a spec-kit feature spec, asks up to five targeted clarification questions, and writes the accepted answers directly back into the spec. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy covering functional scope, data model, UX flows, non-functional attributes, integrations, edge cases, constraints, and terminology, marking each category Clear, Partial, or Missing. - Interactive Questioning Loop: Presents one question at a time (maximum five) as multiple-choice with a recommended option or a constrained short answer, then validates and records each response. - Incremental Spec Updates: Appends each accepted answer to a ## Clarifications session section and applies it to the relevant spec section, saving the file after every integration. - Use Case: Before running /speckit-plan on a new feature branch, run this Skill to resolve open questions about authentication requirements, data retention, and error handling so the implementation plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to identify 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 spec-kit feature specification?▼

Run the speckit-clarify workflow on the active feature branch. It loads the spec via check-prerequisites, scans it against a coverage taxonomy, asks up to five targeted questions one at a time, and writes accepted answers into a Clarifications section of the spec.

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

Run clarification after creating the spec with /speckit-specify and before /speckit-plan. Skipping it is allowed for exploratory spikes, but the workflow warns that downstream rework risk increases when ambiguities remain unresolved.

What project structure does speckit-clarify require?▼

It requires a spec-kit project with a .specify directory containing scripts such as check-prerequisites, plus an active feature spec file. If the spec is missing, it instructs you to run /speckit-specify first rather than creating one.

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each must be answerable as a multiple-choice selection or a short answer of five words or fewer, and retries to disambiguate an answer do not count as new questions.

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

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