speckit-clarify

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc --skill speckit-clarify-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Ab0umar/selrs.cc/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/Ab0umar/selrs.cc --skill speckit-clarify-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguity, missing decisions, and vague requirements that cause rework during planning and implementation. This Skill systematically scans a spec for gaps and resolves them through structured, quota-limited questioning before planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories including functional scope, data model, non-functional requirements, edge cases, and terminology, marking each as Clear, Partial, or Missing. - Interactive Clarification Loop: Asks up to 5 high-impact questions one at a time, offering recommended multiple-choice options or suggested short answers based on best practices. - Incremental Spec Updates: Writes each accepted answer into a ## Clarifications session section and applies it to the relevant spec sections, validating consistency after every save. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about authentication, data retention, or error handling so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to identify 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 speckit-clarify workflow on the active feature spec. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the answers back into 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 in planning, task decomposition, and acceptance test design.

How many clarification questions does the workflow ask?▼

The workflow asks a maximum of 5 questions per session, selected by impact and uncertainty. Each question is either multiple-choice with a recommended option or a short answer constrained to 5 words or fewer.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory and an existing feature spec located via the check-prerequisites script. If no spec exists, you must run /speckit-specify first.

What happens if the spec has no ambiguities?▼

If the coverage scan finds all categories clear, the workflow reports that no critical ambiguities were detected, outputs a compact coverage summary, and suggests proceeding directly to /speckit-plan.