speckit-clarify

Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-clarify-damian-garces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/damian-garces/spec-driven-development/tree/main/spec-driven-project/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-clarify-damian-garces

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 underspecified areas in a spec and resolves them through targeted clarification questions before planning begins. ## 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 answer and multiple-choice or short-answer format. - 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, run this Skill to resolve open questions about security posture, data constraints, or acceptance criteria so downstream planning proceeds on a solid spec. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec 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 skill inside a Spec Kit project. It scans the active feature spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the answers directly into the spec file.

When should I run spec clarification in Spec Kit?

Run clarification after /speckit-specify and before /speckit-plan. Resolving ambiguities at this stage reduces downstream rework risk in planning, task decomposition, and acceptance test design.

How many clarification questions does the skill ask?

It asks a maximum of 5 questions per session, prioritized by impact and uncertainty. Each question is multiple-choice or a short answer of five words or fewer, and you can stop early by saying done or proceed.

Does speckit-clarify work without a Spec Kit project structure?

No. It requires a Spec Kit project with a .specify directory and an existing feature spec created by /speckit-specify. If the spec file is missing, it instructs you to run /speckit-specify first.

What happens to the requirements checklist after clarification?

If FEATURE_DIR/checklists/requirements.md exists, the skill re-evaluates each checkbox item against the updated spec, toggling only markers whose pass/fail state changed, and reports newly passing items, regressions, and remaining gaps.