speckit-clarify

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

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

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 clarification questions one at a time, each with a recommended option and reasoning, then writes accepted answers into a ## Clarifications section of the spec. - Checklist Re-validation: Re-evaluates the spec quality checklist at checklists/requirements.md after updates, reporting newly passing items and regressions. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about authentication, data constraints, or acceptance criteria 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 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 spec-kit?▼

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. It runs check-prerequisites.ps1 to locate FEATURE_DIR and FEATURE_SPEC, and optionally reads .specify/memory/constitution.md and .specify/extensions.yml for hooks.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Each question must be answerable by multiple choice or a short answer of five words or fewer, and retries to disambiguate an answer do not count against the quota.

What happens if the spec file is missing?▼

The workflow aborts and instructs you to run /speckit-specify first. It does not create a new spec file on its own, since clarification only operates on an existing feature specification.