speckit-clarify

Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguities, missing decisions, and vague requirements that cause rework during planning and implementation. This Skill systematically detects those gaps and resolves them through targeted questions before planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories (functional scope, data model, non-functional requirements, edge cases, terminology) and marks each as Clear, Partial, or Missing. - Interactive Questioning Loop: Asks up to 5 high-impact clarification questions one at a time, each with a recommended option or suggested answer, and integrates accepted answers directly into the spec file. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates, reporting newly passing items, regressions, and remaining gaps. - Use Case: After drafting a feature spec with /speckit-specify, run this Skill to resolve open questions about security posture, scale assumptions, and acceptance criteria before invoking /speckit-plan. ## Quick Start Ask the assistant to clarify the current feature spec, optionally naming areas to focus on such as authentication or data retention.

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

Run the clarify command after creating a spec with /speckit-specify. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the accepted answers directly into the spec file.

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

Run clarification after /speckit-specify and before /speckit-plan. Skipping it is allowed for exploratory spikes, but the workflow warns that downstream rework risk increases when ambiguities remain unresolved.

How many clarification questions does the spec-kit clarify command ask?▼

It asks a maximum of 5 questions per session, presented one at a time. Each question is either multiple-choice with a recommended option or a short answer constrained to five words or fewer.

Does spec-kit clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory and an active feature spec located via the check-prerequisites script. If the spec file is missing, it instructs you to run /speckit-specify first.

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/after pass counts plus any regressions.