speckit-clarify

Resolve ambiguities in feature specifications and record clarifications within spec-kit projects.

Updated Mar 25, 2026

Search Tags:#planning #requirements #validation #clarification #ambiguity #spec

Ready to run

npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-clarify-igoorstraviinsky-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/igoorstraviinsky-dev/produtos/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-clarify-igoorstraviinsky-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in feature specifications slow down delivery and increase rework. Speckit-clarify provides a structured workflow to surface, capture, and resolve gaps before planning.

Core Features & Use Cases

Structured ambiguity scanning across functional requirements, data model, UX, and non-functional criteria.
Interactive, capped-questions loop (up to five questions) to drive alignment among stakeholders.
Automatic integration of clarifications into the SPEC (under a Clarifications section) with per-session tracking and validation.

Quick Start

Execute speckit-clarify on the current spec to begin collecting clarifications.

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?▼

To resolve ambiguities in feature specifications, you can use a structured interactive workflow that scans functional requirements, data models, interactions, and non-functional criteria, then records clarifications directly into the spec. This enforces alignment before planning begins.

What is the best way to clarify underspecified requirements in a spec?▼

The best way to clarify underspecified requirements is through an interactive, capped-question loop that limits inquiries to five questions, driving stakeholder alignment while automatically integrating the answers into a Clarifications section of the spec.

How does structured spec clarification prevent rework during early-stage planning?▼

Structured spec clarification prevents rework by surfacing and capturing gaps across functional requirements and non-functional criteria early, validating readiness, and ensuring all stakeholders are aligned before the planning phase initiates.

Can I limit the number of clarification questions asked during specification validation?▼

Yes, you can limit clarification questions during specification validation. The workflow enforces a strict cap of up to five questions per session, ensuring stakeholders face a constrained, efficient alignment process without endless questioning.

Does spec clarification automatically update the original specification document?▼

Yes, spec clarification automatically integrates resolved answers into the original specification document under a dedicated Clarifications section, providing per-session tracking and validating readiness before moving to planning.

When should I not use an interactive Q&A approach for requirement validation?▼

You should not use an interactive Q&A approach for requirement validation when a specification is already fully detailed, as the ambiguity scanning targets underspecified features and the five-question cap may be insufficient for severely incomplete specs.