speckit-clarify

Clarify underspecified feature specs by asking up to five high-impact questions.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-clarify-demersonpolli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/demersonpolli/basic-interpreter/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-clarify-demersonpolli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces ambiguity in a feature specification by asking only the most impactful clarification questions before planning and implementation.

Core Features & Use Cases

  • Ambiguity detection & categorization: Scans the active feature spec across functional scope, data model, UX flow, quality attributes, dependencies, edge cases, constraints, terminology, and measurable completion signals.
  • Up to 5 high-impact clarifications: Selects a prioritized set of questions (max five) that materially affect architecture, test design, operational readiness, or compliance validation.
  • Incremental spec updates: Integrates each accepted answer into the appropriate sections, saves the spec after every answer, and maintains a running clarification log.
  • Guardrails and workflow safety: Validates the spec-kit project prerequisites via the repo script, limits question count, and avoids unnecessary low-impact questions.

Quick Start

Run the speckit-clarify command on your current feature spec and answer the single question prompts until it reports completion or you indicate you are done.

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify ambiguous feature requirements before implementation?▼

Clarify ambiguous feature requirements by interactively answering up to five high-impact questions targeting functional scope, data models, and UX flows, which are then applied directly back into the spec.

What is the best way to resolve underspecified product specifications?▼

Resolve underspecified product specifications by scanning for ambiguity across quality attributes, edge cases, and constraints, then prioritizing clarifications that materially affect architecture and test design.

How do I incrementally update a feature spec during clarification?▼

Incrementally update a feature spec by integrating each accepted clarification answer into the appropriate sections, saving the file after every response, and maintaining a running clarification log.

Does interactive spec clarification work with spec-kit workflows?▼

Interactive spec clarification works with spec-kit workflows by validating active project prerequisites via check-prerequisites, enforcing structured question formats, and persisting incremental updates to the feature spec.

Why are clarification questions limited to five per feature spec?▼

Questions are limited to five per feature spec to ensure only material ambiguities affecting operational readiness, compliance validation, or measurable acceptance criteria are addressed, avoiding unnecessary low-impact queries.