speckit-clarify

Detects underspecified areas in feature specs and records targeted clarification answers into the spec file.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-clarify-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-clarify-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguous requirements, missing decisions, and vague language that cause rework during planning and implementation. This Skill systematically scans a spec-kit feature spec, asks up to five high-impact clarification questions, and writes the accepted answers directly back into the spec. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Questioning Loop: Presents one question at a time with recommended multiple-choice options or suggested short answers, capped at five questions per session. - Incremental Spec Updates: Appends each accepted answer to a 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, data constraints, or acceptance criteria so the plan is built on unambiguous requirements. ## Quick Start Ask the assistant 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 spec-kit feature specification?▼

Run the speckit-clarify workflow on the active feature branch. It scans the spec across categories like functional scope, data model, and non-functional requirements, then asks up to five targeted questions and writes the answers into a Clarifications section of the spec.

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

Run clarification after creating the spec with /speckit-specify and before running /speckit-plan. Resolving ambiguities at this stage reduces downstream rework in planning, task decomposition, and acceptance test design.

How many clarification questions does the workflow ask?▼

The workflow 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.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing the check-prerequisites script and the feature spec. If the spec file is missing, it instructs you to run /speckit-specify first.

What happens to the requirements checklist after clarification?▼

If a requirements.md checklist exists in the feature directory, it is re-validated against the updated spec. Checkbox states are toggled only when items newly pass or regress, and the completion report shows before and after pass counts.