speckit-clarify

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-clarify-speeddesigns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/speeddesigns/cvusd-calendars/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-clarify-speeddesigns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguous requirements, missing decisions, and vague language 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 - Structured Ambiguity Scan: Evaluates the active spec against a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Clarification 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. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates and reports newly passing items, regressions, and outstanding gaps. - Use Case: Before running implementation planning on a new feature, invoke this Skill to resolve open questions about acceptance criteria, data constraints, and error handling so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the 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?

Run the clarify workflow on the active feature spec. It scans the spec against a coverage taxonomy, asks up to 5 targeted questions one at a time, and writes each accepted answer into a Clarifications section of the spec file.

When should I run spec clarification in spec-kit?

Run clarification after creating the spec and before invoking the plan command. Skipping it is allowed for exploratory spikes, but downstream rework risk increases when ambiguities reach the planning phase.

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

No. It requires a .specify directory with the check-prerequisites script and an existing feature spec. If the spec file is missing, it instructs you to run the specify command first rather than creating one.

How many clarification questions can be asked per session?

A maximum of 5 questions per session. Questions are prioritized by impact and uncertainty, and the loop stops early if all critical ambiguities are resolved or the user signals completion.

What happens to the requirements checklist after clarification?

If a requirements.md checklist exists in the feature directory, each checkbox item is re-evaluated against the updated spec. Only markers whose pass/fail state changed are toggled, and the completion report shows before and after pass counts.