speckit-clarify

Identify ambiguities in feature specifications and generate targeted clarification questions.

Updated Feb 13, 2026

Search Tags:#workflow #specification #requirements #product management #clarification #ambiguity

Ready to run

npx skills add https://github.com/magdymohamed78/Wasla --skill speckit-clarify-magdymohamed78

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses underspecified requirements by systematically identifying and resolving ambiguities before the planning phase, reducing downstream rework and ensuring clarity.

Core Features & Use Cases

Ambiguity Detection: Scans specifications against a comprehensive taxonomy to flag unclear or missing information.
Targeted Questioning: Generates a prioritized list of up to five concise, actionable questions to resolve ambiguities.
Incremental Spec Updates: Integrates answers directly back into the specification file, maintaining a clear audit trail.
Use Case: Before planning a new feature, run this skill to ensure all functional scope, non-functional requirements, and edge cases are clearly defined, preventing costly misunderstandings during development.

Quick Start

Use the speckit clarify skill to 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 a feature specification before development?▼

You can resolve ambiguities in a feature specification by scanning it against a taxonomy to identify unclear functional scope, data models, and integrations, then generating targeted questions to incrementally update the document.

What is the best way to identify missing non-functional requirements in a product spec?▼

Identifying missing non-functional requirements in a product spec involves systematically checking the document against a comprehensive taxonomy to flag undefined attributes and edge cases, ensuring clarity before the planning phase begins.

How do I automate generating clarification questions for underspecified requirements?▼

You can automate generating clarification questions for underspecified requirements by using a tool that detects ambiguities and outputs a prioritized list of up to five concise, actionable questions for stakeholders to resolve.

Can I incrementally update a specification document with clarified requirement answers?▼

Yes, you can incrementally update a specification document by integrating accepted answers directly back into the file, which maintains a clear audit trail and ensures the spec reflects the resolved functional scope.

When do I need to run a requirement clarification process for feature planning?▼

You need to run a requirement clarification process for feature planning before the planning phase starts, ensuring all functional scope, non-functional requirements, and edge cases are clearly defined to prevent costly downstream rework.