speckit-clarify

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

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-clarify-ahmedragabrg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/AhmedRagabRG/academy/tree/main/frontend/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-clarify-ahmedragabrg

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 against a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Questioning Loop: Asks one question at a time (maximum 5) with recommended multiple-choice options or suggested short answers, then integrates each accepted answer into the appropriate spec section. - Checklist Re-validation: Re-evaluates the spec quality checklist at checklists/requirements.md after updates and reports newly passing items, regressions, and outstanding gaps. - 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 skill to review the current feature spec and resolve its 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 skill after creating a spec with /speckit-specify. It scans the spec against a coverage taxonomy, asks up to 5 targeted questions one at a time, and writes accepted answers into a Clarifications section and the relevant spec sections.

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

Run it after /speckit-specify and before /speckit-plan. Clarifying first reduces downstream rework risk, since planning decisions depend on resolved requirements. You may skip it for exploratory spikes, but the skill warns about increased rework risk.

What project structure does speckit-clarify require?▼

It requires a spec-kit project with a .specify directory and an active feature branch. It runs .specify/scripts/bash/check-prerequisites.sh to locate FEATURE_DIR and FEATURE_SPEC, and aborts if the spec file is missing.

How many clarification questions can speckit-clarify ask?▼

It asks a maximum of 5 questions per session, selected by impact and uncertainty across categories like security, data model, and edge cases. Each question is multiple-choice or a short answer of five words or fewer.

Does speckit-clarify update the requirements checklist automatically?▼

Yes, if FEATURE_DIR/checklists/requirements.md exists, it re-evaluates each checkbox against the updated spec, toggles only markers whose state changed, and reports before/after pass counts plus newly passing items and regressions.