speckit-clarify

Detects underspecified areas in feature specs and records targeted clarification answers.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-clarify-msaid1976
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/msaid1976/TSP-SmartAIRoute/tree/main/SmartRouteAI/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-clarify-msaid1976

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguity, missing decisions, and vague requirements that cause rework during planning and implementation. This Skill systematically scans a spec for gaps and resolves them through focused clarification 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 option or suggested answer based on best practices. - Incremental Spec Updates: Writes each accepted answer into a ## Clarifications section and updates the relevant spec sections atomically, preserving formatting. - Use Case: Before running /speckit.plan on a new feature spec, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so the plan is built on validated decisions. ## Quick Start Ask the assistant to run the speckit clarify workflow on the current feature spec to identify 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 clarify workflow, which scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions. Each accepted answer is written back into the spec under a Clarifications section.

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

Run clarification after creating a spec with /speckit.specify and before running /speckit.plan. Skipping it increases downstream rework risk because planning decisions may rest on unresolved ambiguities.

How many clarification questions does the workflow ask?▼

The workflow asks a maximum of 5 questions per session, selected by impact and uncertainty. Each question is multiple-choice or a short answer of five words or fewer, and retries do not count toward the limit.

Does speckit-clarify work without a .specify directory?▼

No, it requires a spec-kit project structure with a .specify directory and an existing feature spec. If the spec file is missing, it instructs you to run /speckit.specify first rather than creating one.

What happens to clarification answers after I respond?▼

Each accepted answer is appended as a bullet under a dated Clarifications session heading and applied to the relevant spec section, such as Functional Requirements or Data Model. The spec file is saved after each integration.