speckit-clarify

Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-clarify-lluisfont
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/lluisfont/clickup-reporting/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-clarify-lluisfont

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 resolves them through targeted questions before development begins. ## 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 writes accepted answers into a ## Clarifications section of the spec. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates and reports newly passing items, regressions, and outstanding gaps. - Use Case: Before running implementation planning on a new feature spec, invoke this Skill to resolve open questions about scope, security posture, and acceptance criteria so downstream tasks are built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and resolve its 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 the active spec file. It scans categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the accepted answers directly into a Clarifications section of the spec.

When should I run spec clarification in Spec Kit?

Run clarification after creating the feature spec and before invoking the planning step. Skipping it is allowed for exploratory spikes, but downstream rework risk increases because planning depends on resolved requirements.

How many clarification questions does the workflow ask?

The workflow 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 spec clarification update the requirements checklist?

Yes. If a requirements checklist exists in the feature directory, it re-evaluates each checkbox against the updated spec, toggles only items whose pass/fail state changed, and reports newly passing items, regressions, and remaining gaps.

What happens if the spec file is missing?

The workflow aborts and instructs you to run the specify step first. It never creates a new spec on its own, since clarification only operates on an existing feature specification.