speckit-clarify

Scan feature specs for ambiguity and encode clarification answers into the document.

Updated Apr 2, 2026

Search Tags:#planning #requirements #clarification #ambiguity #speckit #feature-spec

Ready to run

npx skills add https://github.com/programmingworld1/AISpecKit --skill speckit-clarify-programmingworld1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/programmingworld1/AISpecKit/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/programmingworld1/AISpecKit --skill speckit-clarify-programmingworld1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec by prompting up to five highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

Ambiguity & coverage assessment across functional, domain, interaction, non-functional, and edge-case categories.
Interactive, constrained questioning loop (max five questions) with concise, actionable answers.
Automatic updates to the spec under a new "Clarifications" section, with session-scoped notes for traceability.

Quick Start

Load your current feature spec and start the interactive clarification session to answer up to five targeted questions.

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clarify ambiguous requirements in a feature spec?▼

To clarify ambiguous requirements in a feature spec, load your active spec to start an interactive session that asks up to five targeted questions across functional, domain, interaction, non-functional, and edge-case categories. Answers are appended directly into a Clarifications section.

What is an ambiguity and coverage scan for feature specifications?▼

An ambiguity and coverage scan for feature specifications is a structured assessment that identifies underspecified areas across functional, domain, interaction, non-functional, and edge-case categories. It generates targeted clarification questions to resolve gaps and update the spec automatically.

How do I find missing edge cases in my product requirements?▼

To find missing edge cases in product requirements, run a structured ambiguity scan on your feature spec. The tool evaluates coverage across multiple categories and prompts up to five focused questions to surface and resolve underspecified edge-case scenarios.

Does spec clarification work with existing feature specs or do I need a specific format?▼

Spec clarification works with your existing feature specs by loading the active document directly. There are no external dependencies required; the tool scans the loaded spec content and appends resolved answers under a new top-level Clarifications section.

What's the best way to document requirement clarifications without losing traceability?▼

The best way to document requirement clarifications without losing traceability is to append answers to a dedicated Clarifications section in the spec while applying them to relevant sections. The tool also maintains session-scoped notes for full traceability of each accepted answer.

Can I limit the number of clarification questions asked during a spec review?▼

Yes, you can limit clarification questions during a spec review because the interactive questioning loop is constrained to a maximum of five highly targeted questions. This ensures the ambiguity scan remains focused and actionable without overwhelming the user.