speckit-clarify

Detect and reduce ambiguities in feature specifications via structured clarification questions.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-clarify-a2mus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-clarify-a2mus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and reduces ambiguity in underspecified feature specifications so planning and implementation proceed with clear, testable acceptance criteria and minimal rework.

Core Features & Use Cases

  • Structured ambiguity scanning: Performs a coverage-based taxonomy scan across functional scope, data model, UX flows, non-functional attributes, integrations, edge cases, constraints, and terminology.
  • Prerequisite discovery: Runs the specified check-prerequisites script to locate FEATURE_DIR and FEATURE_SPEC and captures context needed for targeted questions.
  • Interactive, prioritized questioning: Produces a prioritized queue of concise, answerable clarification questions (limited quota), recommends answers, accepts user input, and records each accepted answer.
  • In-place spec integration & validation: Creates a Clarifications session in the spec, appends one bullet per accepted answer, updates relevant sections, validates structure, and saves the FEATURE_SPEC atomically after each integration.
  • Use case: Run before planning to convert vague requirements into actionable, measurable acceptance criteria and data model changes.

Quick Start

Clarify the active feature spec by generating prioritized questions, capturing answers, and appending them under a new Clarifications session in FEATURE_SPEC.

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 feature specifications before planning?

To resolve ambiguities in feature specifications, you can use a structured clarification workflow that scans functional scope, data models, and UX flows to generate prioritized, answerable clarification questions and record accepted answers directly into the spec.

How do I detect and clarify underspecified requirements in a spec-kit repository?

Detecting underspecified requirements involves running a prerequisite script to locate the FEATURE_SPEC, scanning across functional scope and edge cases, and interactively capturing answers to append them under a new Clarifications session in the repository.

What is the best way to convert vague feature requirements into testable acceptance criteria?

The best way to convert vague requirements into testable acceptance criteria is through an interactive, prioritized questioning process that captures accepted answers and updates relevant spec sections atomically after each integration.

Do I need write permissions to run a spec clarification workflow on a feature repository?

Yes, you need write permissions to update the FEATURE_SPEC file, alongside access to the repository .specify directory and the ability to run the check-prerequisites script to capture the necessary context.

Can I interactively record clarification answers directly into FEATURE_SPEC?

Yes, you can interactively record answers directly into FEATURE_SPEC by appending one bullet per accepted answer under a new Clarifications session, validating the structure, and saving the file atomically after each integration.