speckit-clarify

Identifies underspecified areas in feature specs and integrates clarification answers into the spec file.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-clarify-carl-fabri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Carl-Fabri/TestAngularSpecDriven/tree/main/test-angular/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-clarify-carl-fabri

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-kit feature spec and resolves them through targeted clarification questions 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 Questioning Loop: Asks up to 5 high-impact clarification questions one at a time, each with a recommended option or suggested answer based on best practices. - Incremental Spec Integration: Writes each accepted answer back into the spec under a Clarifications section and updates the relevant requirement sections, then re-validates the spec quality checklist. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so the plan is built on unambiguous requirements. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and clarify any ambiguous requirements 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 spec-kit feature specification?

Run the speckit-clarify skill after creating a spec with /speckit-specify. 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 file.

When should I run spec clarification in a spec-driven workflow?

Run clarification after /speckit-specify and before /speckit-plan. Clarifying first reduces downstream rework because the implementation plan and tasks are generated from an unambiguous specification.

What project structure does speckit-clarify require?

It requires a spec-kit project with a .specify directory, including the check-prerequisites PowerShell script and an active feature spec. If the spec file is missing, it instructs you to run /speckit-specify first.

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 clarification update the spec quality checklist automatically?

Yes. If FEATURE_DIR/checklists/requirements.md exists, each checkbox item is re-evaluated against the updated spec, and only markers whose pass/fail state changed are toggled, with before/after counts reported.