speckit-clarify

Identify and resolve ambiguities in feature specs through targeted clarification questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and unresolved placeholders that cause rework during planning and implementation. This Skill systematically scans a spec for underspecified areas and encodes stakeholder answers directly back into the spec file. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories including functional scope, data model, non-functional requirements, edge cases, and terminology, marking each as Clear, Partial, or Missing. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended multiple-choice option or suggested short answer grounded in best practices. - Incremental Spec Integration: Writes each accepted answer into a Clarifications section and updates the relevant spec sections atomically, then re-validates the requirements checklist. - Use Case: Before running implementation planning on a new feature spec, run this Skill to resolve open questions about security posture, data constraints, and acceptance criteria so downstream tasks are built on confirmed decisions. ## Quick Start Ask the assistant to run speckit-clarify on the current feature spec to find and resolve its biggest ambiguities.

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 on your spec file, which scans categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions. Accepted answers are written directly into a Clarifications section and the relevant spec sections.

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 and task decomposition depend on resolved requirements.

What project structure does spec clarification require?▼

It requires a spec-kit project with a .specify directory containing scripts and the active feature spec. The prerequisite check script must return valid JSON paths, otherwise you need to re-run the specify step first.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session, selected by impact and uncertainty across unresolved categories. Each question is multiple-choice or a short answer of five words or fewer, with a recommended option provided.

Does clarification update the requirements checklist automatically?▼

Yes, if a checklists/requirements.md file exists in the feature directory, each checkbox item is re-evaluated against the updated spec. Only markers whose pass/fail state changed are toggled, and a before/after summary is reported.