speckit-clarify

Identify underspecified areas in feature specs and record clarified answers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature specification by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

  • Taxonomy-guided ambiguity detection across functional scope, data model, UX flows, non-functional quality attributes, integration points, edge cases, and terminology.
  • Interactive, one-question-at-a-time looping: generates a concise set of questions (max 5) prioritized by impact and uncertainty and records accepted answers back into the spec immediately.
  • In-context integration: after each answer, updates a Clarifications section with a dated session and validates consistency to prevent drift, then saves the spec atomically.
  • Prerequisite validation and spec-loading: ensures the repo environment and current spec are ready before prompting clarifications.
  • Outcome-oriented traceability: produces a minimal, testable record of decisions and rationale to support downstream planning and implementation.

Quick Start

Invoke the clarification workflow to surface the top ambiguities in the active spec and commit each clarified answer to the spec file.

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 and gaps in a feature specification?

To identify ambiguities in a feature specification, you can use a taxonomy-guided workflow that analyzes functional scope, data model, UX, and edge cases to generate prioritized clarification questions. This targets underspecified areas efficiently.

What is the best way to clarify requirements and record decisions back into a spec?

The best way to clarify requirements is an interactive, one-question-at-a-time loop that updates a Clarifications section immediately. It validates consistency to prevent drift and saves the spec atomically after each accepted answer.

Do I need a spec-kit directory structure to run automated spec clarification?

Yes, automated spec clarification requires a spec-kit project environment with a .specify/ directory. The workflow validates this prerequisite and loads the current active spec before prompting any targeted clarification questions.

How many clarification questions will be generated for my spec?

The workflow generates a maximum of five clarification questions per session. These questions are prioritized by impact and uncertainty across functional scope, data model, UX flows, integration points, and edge cases.

How does clarifying a specification help with downstream implementation?

Clarifying a specification produces a minimal, testable record of decisions and rationale. This outcome-oriented traceability supports downstream planning and implementation by ensuring the active spec has no underspecified areas.