speckit-clarify

Detects ambiguities in feature specifications and records targeted clarification answers into the spec file.

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-clarify-sensein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/sensein/senselab --skill speckit-clarify-sensein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and undefined edge cases that cause rework during planning and implementation. This Skill systematically scans a spec-kit feature specification, identifies underspecified areas, and resolves them through up to five targeted clarification questions whose answers are written directly back into the spec. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec against a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, constraints, and terminology. - Interactive Questioning Loop: Asks one question at a time (maximum five) with recommended multiple-choice options or constrained short answers, prioritizing high-impact unresolved categories. - Incremental Spec Updates: Appends each accepted answer to a dated Clarifications section and applies it to the relevant spec sections, saving after every integration. - Use Case: Before running /speckit.plan on a new feature branch, run this Skill to resolve open questions about security posture, data entities, and acceptance criteria so the implementation plan is built on unambiguous requirements. ## Quick Start Run the speckit-clarify skill to review my current feature specification and ask me targeted questions to 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 clarification workflow on your spec file, which scans it against a taxonomy of categories like functional scope, data model, and edge cases. It then asks up to five targeted questions and writes your answers directly into a Clarifications section of the spec.

When should I run spec clarification in spec-kit?

Run clarification after /speckit.specify and before /speckit.plan. Resolving ambiguities first reduces downstream rework risk, since planning and task decomposition depend on unambiguous requirements and testable acceptance criteria.

What are the requirements for running speckit-clarify?

It requires a spec-kit project structure with a .specify directory and an existing feature spec created by /speckit.specify. The workflow calls check-prerequisites.sh to locate the feature directory and spec file, and aborts if the spec is missing.

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 retries to disambiguate an answer do not count toward the limit.

What happens if no ambiguities are found in the spec?

If the coverage scan finds all categories clear or only low-impact gaps, the workflow reports that no critical ambiguities were detected, outputs a compact coverage summary, and suggests proceeding directly to the planning step.