speckit-clarify

Identify and resolve ambiguities in feature specifications through targeted clarification questions.

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-clarify-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-clarify-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and unresolved edge cases that cause rework during implementation. This Skill systematically scans a spec for underspecified areas and resolves them through up to five targeted clarification questions, writing the answers directly back into the spec file. ## 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 one question at a time with recommended multiple-choice options or suggested short answers, capped at five questions per session. - Incremental Spec Updates: Records each accepted answer under a dated Clarifications section and applies it to the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running implementation planning on a new feature spec, invoke this Skill to surface hidden ambiguities—such as undefined scale assumptions or missing error-handling behavior—and encode the decisions directly into the spec. ## Quick Start Ask the assistant to clarify the current feature spec, optionally naming specific areas to focus on, such as security or data model.

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 five targeted questions and writes the accepted answers directly back into the spec under a Clarifications section.

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

Run clarification after creating the spec with speckit-specify and before running speckit-plan. Clarifying first reduces downstream rework risk, since unresolved ambiguities in the spec propagate into implementation plans and task breakdowns.

Does spec clarification require a spec-kit project structure?▼

Yes, it requires a .specify directory with the spec-kit project structure, including the check-prerequisites script that locates the feature spec. If the spec file is missing, you must run speckit-specify first.

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each question must be answerable with a multiple-choice selection or a short answer of five words or fewer, and only questions that materially impact architecture, data modeling, or testing are asked.

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 actually changed are toggled, and the completion report shows before and after pass counts.