speckit-clarify

Identifies underspecified areas in feature specs through targeted clarification questions.

Updated May 28, 2026
One-click install
npx skills add https://github.com/whw23/PingoGate --skill speckit-clarify-whw23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/whw23/PingoGate/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/whw23/PingoGate --skill speckit-clarify-whw23

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 underspecified areas in a spec-kit feature spec and resolves them through structured, interactive clarification before planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec against a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, constraints, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended option or suggested answer grounded in best practices. - Incremental Spec Updates: Writes each accepted answer back into the spec under a Clarifications section and updates the relevant requirement sections atomically. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, scale targets, and edge-case handling so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to clarify the current feature spec, optionally naming areas to focus on such as security or data model.

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 after creating a spec with /speckit-specify. It scans the spec against a coverage taxonomy, asks up to five targeted questions one at a time, and writes accepted answers directly back into the spec file.

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

Run clarification after /speckit-specify and before /speckit-plan. Resolving ambiguities first reduces downstream rework risk in planning, task decomposition, and acceptance test design.

What project structure does spec clarification require?▼

It requires a spec-kit project with a .specify directory and an active feature branch. The skill runs check-prerequisites.sh to locate the feature spec, and aborts with guidance if the spec file is missing.

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each question must be answerable as a multiple-choice selection or a short answer of five words or fewer, prioritized by impact and uncertainty.

What happens to clarification answers after I respond?▼

Each accepted answer is appended to a Clarifications section with a dated session heading, then applied to the relevant spec sections such as Functional Requirements, Data Model, or Success Criteria, and saved atomically.