speckit-clarify

Identify ambiguities in feature specifications and generate prioritized clarification questions.

Updated Feb 22, 2026

Search Tags:#feature definition #risk reduction #requirements clarification #ambiguity detection #interactive q&a #specification quality

Ready to run

npx skills add https://github.com/szaher/agentspec --skill speckit-clarify-szaher

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses underspecified requirements by proactively identifying and resolving ambiguities before the planning phase, reducing rework risk.

Core Features & Use Cases

Ambiguity Detection: Scans feature specifications against a taxonomy of common ambiguity types.
Targeted Questioning: Generates prioritized, concise questions to clarify missing details.
Incremental Spec Update: Integrates answers directly into the specification file.
Use Case: Before planning a new feature, run this skill to ensure all functional scope, data models, and non-functional requirements are clearly defined, preventing costly misunderstandings later.

Quick Start

Run the speckit-clarify skill to identify and resolve ambiguities in the current feature specification.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I resolve ambiguities in feature specifications before planning?▼

Resolving ambiguities in feature specifications involves scanning requirements against a taxonomy to identify underspecified functional scope, data models, and non-functional attributes, then generating prioritized questions for interactive clarification to prevent rework.

What is requirements clarification and why does it reduce project risk?▼

Requirements clarification is the process of proactively detecting and resolving underspecified details in feature specs before the planning phase, which reduces project risk by preventing costly misunderstandings and rework later in development.

How do I detect missing details in a feature specification?▼

Detecting missing details in a feature specification requires scanning the document using a coverage-based taxonomy to identify ambiguities across functional scope, user interactions, and non-functional attributes, followed by targeted questioning.

Can I incrementally update a spec file through interactive Q&A?▼

Yes, you can incrementally update a specification file by integrating answers from prioritized interactive Q&A directly into the document, ensuring all functional scope and data models are clearly defined and tracking final coverage.

What is the best way to ensure specification quality before development?▼

Ensuring specification quality before development requires running a structured clarification process that identifies ambiguities across functional scope and non-functional requirements, resolving them through interactive questions and incremental spec updates.