speckit-clarify

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-clarify-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-clarify
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-clarify-eovipmak

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 planning begins. ## 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, and encodes accepted answers directly into the spec file. - Incremental Spec Updates: Maintains a Clarifications section, updates affected sections atomically, and re-validates the spec quality checklist after each change. - Use Case: Before running speckit-plan on a new feature, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to clarify the current feature spec and resolve any 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?

Run the clarify workflow on your spec file to scan it against a structured taxonomy of categories like functional scope, data model, and edge cases. It asks up to 5 targeted questions and writes the accepted answers directly into the spec.

When should I run spec clarification in spec-kit?

Run clarification after creating the spec with speckit-specify and before running speckit-plan. Skipping it increases downstream rework risk, though you may proceed explicitly for exploratory spikes.

How many clarification questions does the workflow ask?

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

Does spec clarification update the requirements checklist?

Yes, if a requirements.md checklist exists in the feature directory, it re-evaluates each checkbox against the updated spec and toggles only markers whose pass/fail state changed, reporting before and after counts.

What happens if no ambiguities are found in the spec?

If all taxonomy categories are clear, the workflow reports that no critical ambiguities were detected, outputs a compact coverage summary, and suggests proceeding to the planning step.