speckit-clarify

Detects and resolves ambiguities in feature specifications through targeted clarification questions.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Sergiotsk/Interstellar --skill speckit-clarify-sergiotsk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Sergiotsk/Interstellar/tree/main/interstellar/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Sergiotsk/Interstellar --skill speckit-clarify-sergiotsk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and ambiguous terminology that cause rework during planning and implementation. This Skill systematically scans a spec for underspecified areas and encodes clarified answers directly back into the spec file. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec against a taxonomy covering functional scope, data model, UX flows, non-functional attributes, integrations, edge cases, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended multiple-choice option or suggested short answer. - Incremental Spec Updates: Records each accepted answer under a Clarifications section and applies it to the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running implementation planning on a new feature spec, use this Skill to resolve open questions about security posture, scale assumptions, and acceptance criteria so downstream plans are built on confirmed decisions. ## Quick Start Ask the assistant to run speckit-clarify on the current feature spec to identify and resolve underspecified areas before planning.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguities in a feature specification?▼

Run the clarify workflow on the active feature spec. It scans the spec against a structured taxonomy, asks up to 5 targeted questions one at a time, and writes each accepted answer back into the spec under a Clarifications session heading.

When should I run spec clarification in spec-kit?▼

Run clarification after creating the spec with speckit-specify and before invoking speckit-plan. Skipping it is allowed for exploratory spikes, but downstream rework risk increases because plans inherit unresolved ambiguities.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts and the feature spec. It runs check-prerequisites.ps1 to resolve FEATURE_DIR and FEATURE_SPEC paths, and aborts if the spec file is missing.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Each question must be answerable with a multiple-choice selection or a short answer of five words or fewer, and only high-impact ambiguities are prioritized.

What happens to the requirements checklist after clarification?▼

If FEATURE_DIR/checklists/requirements.md exists, each checkbox item is re-evaluated against the updated spec. Only markers whose pass/fail state changed are toggled, and the completion report shows before and after pass counts.