speckit-clarify

Name: speckit-clarify
Availability: InStock
Author: SorinS

Detect underspecified areas in feature specifications and encode clarifications.

Updated Jul 2, 2026

Search Tags:#code quality #ambiguity detection #specification clarity #spec-Driven Development #feature spec analysis

Ready to run

npx skills add https://github.com/SorinS/go-speckit --skill speckit-clarify-sorins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/SorinS/go-speckit/tree/main/testdata/golden/scaffold/proj-vibe/.vibe/skills/speckit-clarify
Command: npx skills add https://github.com/SorinS/go-speckit --skill speckit-clarify-sorins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-kit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The 'speckit-clarify' Skill unit tackles the issue of ambiguity and incomplete decision points within a feature specification by prompting targeted clarifications, thus improving the precision of project plans.

Core Features & Use Cases

Identifies Ambiguities: Discovers areas needing clarification within feature specs.
User Interaction: Guides users through an interactive process of asking up to 5 clarification questions.
Documentation Integration: Records answers back into the spec, ensuring alignment and comprehensiveness.

Quick Start

Invoke the speckit-clarify Skill in your project environment to automatically pinpoint underspecified areas and begin the clarification process.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I detect ambiguity in a feature specification?▼

To detect ambiguity in a feature specification, analyze the document to pinpoint underspecified areas and incomplete decision points. This clarification process identifies gaps and asks up to five targeted questions to improve the precision of your project plans.

What is spec-driven development and how does specification clarity improve it?▼

Specification clarity in spec-driven development ensures feature specs contain precise decisions rather than vague requirements. Identifying underspecified areas and prompting targeted clarifications prevents implementation errors and aligns project plans with actual feature expectations.

Does speckit-clarify work within a spec-kit project directory?▼

Yes, speckit-clarify operates within the .specify directory structure of a spec-kit project. It supports integration with hooks for preprocessing and post-processing clarifications, encoding results directly into the existing specification framework.

How do I resolve incomplete decision points in feature spec analysis?▼

To resolve incomplete decision points in feature spec analysis, run an interactive clarification process that asks up to five targeted questions. This identifies ambiguities and records the answers back into the specification to ensure comprehensiveness and alignment.

What is the maximum number of clarification questions for ambiguity detection?▼

The maximum number of clarification questions for ambiguity detection is five. This limit ensures the process remains focused while adequately resolving underspecified areas and encoding the results back into the feature specification.

Can I use hooks for preprocessing specifications before clarifying ambiguities?▼

Yes, you can use hooks for preprocessing specifications before clarifying ambiguities. The system supports hook integration within the spec-kit directory structure, allowing you to manage both preprocessing and post-processing of feature spec clarifications.