speckit-clarify

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-clarify-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/speckit-clarify
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-clarify-base-analitica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and ambiguous terminology that cause rework during planning and implementation. This Skill systematically scans a spec for underspecified areas and encodes 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 up to 5 high-impact clarification questions one at a time, each with a recommended option or suggested answer. - Incremental Spec Updates: Writes each accepted answer into a Clarifications section and updates the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running implementation planning on a new feature spec, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so downstream tasks are built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to find 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 feature specification?▼

Run the clarify workflow, which scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions. Each accepted answer is written directly into the spec's Clarifications section and relevant requirement sections.

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, since unresolved ambiguities propagate into task decomposition and acceptance tests.

What project structure does spec-kit clarification require?▼

It requires a spec-kit project with a .specify directory containing scripts like check-prerequisites and the feature spec file. If the spec file is missing, you must run speckit-specify first.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session, asked one at a time. Questions are prioritized by impact and uncertainty, and each must be answerable via multiple choice or a short answer of five words or fewer.

Does clarification update the requirements checklist automatically?▼

Yes. If a requirements.md checklist exists in the feature directory, each checkbox item is re-evaluated against the updated spec, and only markers whose pass/fail state changed are toggled.