speckit-clarify

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-clarify-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-clarify-acarmonag

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-kit feature spec, asks up to 5 high-impact clarification questions, and writes the answers directly back into the spec. ## 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 one question at a time (multiple-choice with a recommended option, or short answer with a suggestion), limited to 5 questions per session. - Incremental Spec Updates: Appends each accepted answer to a ## Clarifications session 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, scale assumptions, and acceptance criteria so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and clarify any underspecified areas 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 skill after creating a spec with /speckit-specify. It scans the spec across categories like functional scope, data model, and non-functional requirements, then asks up to 5 targeted questions and writes the answers back into the spec file.

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

Run clarification after /speckit-specify and before /speckit-plan. Resolving ambiguities first reduces downstream rework risk in planning, task decomposition, and acceptance test design. You may skip it for exploratory spikes, but rework risk increases.

How many clarification questions does the skill ask per session?▼

The skill 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 5 words or fewer, and retries do not count toward the limit.

Does speckit-clarify work without a .specify directory?▼

No, it requires a spec-kit project structure with a .specify directory. It runs check-prerequisites scripts to locate the feature spec, and if the spec file is missing it instructs you to run /speckit-specify first rather than creating one.

What happens to the requirements checklist after clarification?▼

If FEATURE_DIR/checklists/requirements.md exists, the skill re-evaluates every checkbox item against the updated spec. It toggles only markers whose pass/fail state changed and reports newly passing items, regressions, and remaining unchecked items.