speckit-clarify

Name: speckit-clarify
Availability: InStock
Author: ahmedemad3

Plan and execute structured clarifications to resolve spec ambiguities and record outcomes.

60|12|Updated Apr 2, 2026

Search Tags:#workflow #planning #specification #requirements #ambiguity #spec-kit #clarify

Ready to run

npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill speckit-clarify-ahmedemad3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/ahmedemad3/super-ai-agency-framework/tree/main/.agent/skills/speckit-clarify
Command: npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill speckit-clarify-ahmedemad3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured clarification workflow to identify and resolve underspecified requirements and record answers directly in the spec clarifications section.

Core Features & Use Cases

Ambiguity detection and coverage scoring across core scope, domain model, interaction flows, non-functional attributes, and edge cases.
Generate a prioritized queue of clarifying questions (up to 5) and integrate accepted answers into the spec as traceable bullets.
Update the spec's Clarifications section with session-specific bullets and ensure terminologies remain consistent.

Quick Start

Initiate a clarifications session against the current spec and capture explicit answers in the Clarifications section.

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 software feature specification?▼

To resolve ambiguities in a feature specification, you can run a structured clarification workflow that detects coverage gaps across functional, data, and UX domains, then records the accepted answers directly in the spec file. This ensures underspecified requirements become traceable bullets.

What is structured clarification in requirements planning?▼

Structured clarification in requirements planning is a targeted process to uncover underspecified functional, non-functional, and edge-case gaps. It generates a prioritized queue of clarifying questions and integrates the explicit answers into the specification to ensure testable, measurable outcomes.

How do I document clarifications and acceptance criteria in a spec file?▼

You document clarifications by generating a prioritized queue of questions, capturing the explicit answers, and updating the spec's Clarifications section with session-specific bullets. This maintains terminology consistency and ensures roles and acceptance criteria remain traceable.

Do I need a specific directory structure to manage specification clarifications?▼

Yes, managing specification clarifications requires a .specify directory structure and YAML frontmatter metadata in the SKILL.md file. This environment setup is necessary to execute the clarification workflow and record outcomes properly within the active feature specification.

What is the best way to identify edge-case gaps in requirements planning?▼

The best way to identify edge-case gaps in requirements planning is to use a structured clarification workflow that scores ambiguity coverage across core scope, domain model, and interaction flows. This systematically targets and highlights missing edge-case definitions in the spec.