speckit-clarify

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-clarify-argoss84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Argoss84/Kando-Caracter-sheet-generator/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-clarify-argoss84

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 encodes the answers directly back into the spec file. ## 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, then integrates accepted answers into a ## Clarifications section and the relevant spec sections. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates and reports newly passing items, regressions, and outstanding gaps. - Use Case: Before running /speckit-plan on a new feature spec, run this Skill to resolve open questions about user roles, data constraints, and acceptance criteria so the plan is built on firm requirements. ## 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 Spec Kit feature spec?▼

Run the speckit-clarify workflow on the active feature branch. 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 back into the spec file.

When should I run spec clarification in a spec-driven workflow?▼

Run clarification after creating the spec with /speckit-specify and before running /speckit-plan. Skipping it is allowed for exploratory spikes, but downstream rework risk increases if high-impact ambiguities remain unresolved.

How many clarification questions does the workflow 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 speckit-clarify require a specific project structure?▼

Yes, it requires a Spec Kit project with a .specify directory, the check-prerequisites PowerShell script, and an existing feature spec. If the spec is missing, it instructs you to run /speckit-specify first.

What happens to the spec quality 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 and any regressions.