speckit-clarify

Detects specification ambiguities and integrates targeted clarification answers into feature specs.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-clarify-nasalciuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Nasalciuc/ATS-HERO/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/Nasalciuc/ATS-HERO --skill speckit-clarify-nasalciuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and ambiguous terminology that cause rework during planning and implementation. This Skill systematically scans a spec for underspecified areas and resolves them through targeted questions before planning begins. ## 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 clarification questions one at a time, each with a recommended option or suggested answer, and encodes accepted answers directly into the spec file. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates, reporting 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 security posture, data constraints, and acceptance criteria so downstream tasks are 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 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 a spec-kit workflow?▼

Run clarification after creating the feature spec and before invoking the planning step. Skipping it increases downstream rework risk, since unresolved ambiguities propagate into task decomposition and acceptance tests.

What project structure does spec clarification require?▼

It requires a spec-kit project with a .specify directory containing the feature spec and prerequisite scripts. If the spec file is missing, you must run the specify command first to generate it.

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 spec quality checklist automatically?▼

Yes, if a requirements checklist 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 the completion report shows before and after pass counts.