speckit-clarify

Identify underspecified areas in feature specs through targeted clarification questions.

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

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 scans the active spec, detects gaps across a structured taxonomy, and resolves them by asking up to five targeted questions whose answers are written back into the spec file. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across categories like functional scope, data model, non-functional requirements, edge cases, and terminology, marking each Clear, Partial, or Missing. - Interactive Questioning Loop: Asks one question at a time (maximum five) with recommended multiple-choice options or suggested short answers, each with a plain-language rationale. - Incremental Spec Integration: Records each accepted answer under a dated 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 assumptions, and acceptance criteria so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and clarify any underspecified areas 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 specification?▼

Run the speckit-clarify skill from the repo root. It loads the current feature spec via check-prerequisites.sh, scans for underspecified areas, asks up to five targeted questions, and writes the 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 skill warns that downstream rework risk increases when ambiguities reach the planning stage.

Does speckit-clarify require a specific project structure?▼

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

How many clarification questions does the skill ask?▼

It asks a maximum of five 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.

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.

Why does the requirements checklist change after clarification?▼

If FEATURE_DIR/checklists/requirements.md exists, the skill re-evaluates every checkbox against the updated spec and toggles only markers whose pass/fail state changed, reporting newly passing items and regressions.