speckit-clarify

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

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/stefaniuk/loadout --skill speckit-clarify-stefaniuk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/stefaniuk/loadout/tree/main/.github/skills/speckit-clarify
Command: npx skills add https://github.com/stefaniuk/loadout --skill speckit-clarify-stefaniuk

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 covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended answer and multiple-choice or short-answer format. - Incremental Spec Updates: Writes each accepted answer into a Clarifications section and updates the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, scale targets, and edge cases so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to find and resolve ambiguities 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 speckit-clarify workflow on the active feature spec. It scans the spec across categories like functional scope, data model, and non-functional requirements, then asks up to 5 targeted questions and writes the answers back into the spec file.

When should I run spec clarification in a 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.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory and an active feature spec created by /speckit-specify. It also checks the workflow mode and only runs when the active mode is speckit, not superpowers.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Questions are prioritized by impact and uncertainty, and each must be answerable with a multiple-choice selection or a short answer of five words or fewer.

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.