speckit-clarify

Identifies and resolves ambiguities in feature specifications via taxonomy-based scan and interactive questions.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill speckit-clarify-dengnaichen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/DengNaichen/Stet --skill speckit-clarify-dengnaichen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the common issue of underspecified feature requirements by identifying gaps in logic, scope, and edge cases before development begins.

Core Features & Use Cases

  • Ambiguity Detection: Scans feature specifications against a comprehensive taxonomy to pinpoint missing or vague requirements.
  • Targeted Clarification: Generates up to 5 high-impact questions to resolve uncertainties in functional scope, data models, and non-functional constraints.
  • Automated Integration: Automatically updates the feature specification file with the clarified answers, ensuring the documentation remains the single source of truth.

Quick Start

Invoke the speckit-clarify skill to analyze the current feature specification and resolve any critical ambiguities.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I resolve ambiguity in feature specifications before development?

To clarify feature specifications, scan requirements against a structured taxonomy to detect missing logic and edge cases, then generate targeted questions to resolve uncertainties before development begins.

What is taxonomy-based ambiguity detection in software engineering?

Taxonomy-based ambiguity detection is a process that evaluates feature specifications against a comprehensive classification system to identify vague requirements and gaps in functional scope before implementation.

Do I need a specific project structure to scan feature specifications for missing requirements?

Yes, scanning feature specifications for missing requirements requires a valid spec-kit project structure containing a .specify directory to execute prerequisite checks and automatically update documentation.

How do I update feature specification files with clarified requirements?

Update feature specification files with clarified requirements by conducting interactive questioning to resolve uncertainties, then automatically integrating the answers back into the documentation to maintain a single source of truth.

How many clarification questions are generated for underspecified feature requirements?

Up to 5 high-impact clarification questions are generated for underspecified feature requirements to resolve uncertainties in functional scope, data models, and non-functional constraints.