speckit-clarify

Identifies ambiguities in feature specifications and generates targeted clarification questions for spec-kit projects.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Elmarbouhe/chez-yema --skill speckit-clarify-elmarbouhe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Elmarbouhe/chez-yema/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/Elmarbouhe/chez-yema --skill speckit-clarify-elmarbouhe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps to identify and address underspecified areas in a feature specification by asking targeted clarification questions.

Core Features & Use Cases

  • Ambiguity Detection: Identifies ambiguous or missing decision points in the spec.
  • Question Generation: Encodes answers back into the spec.
  • Compatibility: Requires spec-kit project structure.
  • Use Case: Use the /speckit-clarify command to detect underspecified areas and enhance your feature spec.

Quick Start

Run /speckit-clarify to begin clarifying your 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 identify ambiguities in a feature specification?

To identify ambiguities in a feature specification, you can use a structured clarification workflow that analyzes the spec and asks up to 5 targeted questions to resolve underspecified areas and missing decision points.

What is the best way to clarify underspecified areas in spec-kit projects?

The best way to clarify underspecified areas in spec-kit projects is by running a targeted question workflow that detects ambiguity and encodes the answers directly back into your feature specification to minimize rework risk.

Does spec-kit feature development require a specific project structure for clarification?

Yes, spec-kit feature development clarification requires a compatible spec-kit project structure to successfully analyze the feature specification and encode the resolved answers back into the document.

How do I reduce downstream rework risk when writing feature specifications?

You can reduce downstream rework risk in feature specifications by detecting ambiguous decision points early and encoding targeted clarification answers directly back into the spec to ensure full development coverage.

Can I generate clarification questions for missing decision points in my spec?

Yes, you can generate clarification questions for missing decision points by analyzing the feature specification to detect ambiguity and producing a maximum of 5 targeted questions to resolve them.