speckit-clarify

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

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/Fras0/clinics-api --skill speckit-clarify-fras0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Fras0/clinics-api/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/Fras0/clinics-api --skill speckit-clarify-fras0

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 encodes the answers directly back into the spec before planning begins. ## 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, 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 /speckit-plan on a new feature spec, run this Skill to resolve open questions about security posture, data constraints, or 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 identify 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 speckit-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 plus the relevant spec sections.

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 in planning, task decomposition, and acceptance test design.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Questions are prioritized by impact and uncertainty, and retries or disambiguation follow-ups on the same question do not count toward the limit.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory. It runs check-prerequisites.ps1 to locate the feature spec and optionally reads .specify/memory/constitution.md and .specify/extensions.yml for hooks.

What happens if no ambiguities are found in the spec?▼

The workflow reports that no critical ambiguities were detected, outputs a compact coverage summary showing all categories as Clear, and suggests proceeding to the planning step.