speckit-clarify

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/dperussina/function2agent --skill speckit-clarify-dperussina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/dperussina/function2agent/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/dperussina/function2agent --skill speckit-clarify-dperussina

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 scans a spec for gaps and resolves them through up to five targeted clarification questions, writing the answers directly back into the spec file. ## 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 one question at a time (maximum five), each with a recommended option or suggested answer, and integrates accepted answers into the spec incrementally. - Checklist Re-validation: Re-evaluates the spec quality checklist at checklists/requirements.md after updates, reporting newly passing items and regressions. - 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 agent to run the speckit-clarify workflow on the current feature spec to identify 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 feature specification?▼

Run the clarify workflow, which scans the spec against a coverage taxonomy and asks up to five targeted questions. Each accepted answer is written back into the spec under a Clarifications section and applied to the relevant requirements sections.

When should I run spec clarification in spec-kit?▼

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

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each question must be answerable with a multiple-choice selection or a short answer of five words or fewer, and retries on the same question do not count toward the limit.

Does speckit-clarify work without a spec-kit project structure?▼

No. It requires a .specify directory with the feature spec located via the check-prerequisites script. If the spec file is missing, it instructs you to run /speckit-specify first rather than creating a new spec.

What happens to the requirements 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 and after pass counts.