speckit-clarify

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-clarify-secrakib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/secrakib/rag-eval-project/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-clarify-secrakib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguities, vague adjectives, and missing decision points 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 (multiple-choice or short answer) with a recommended option and reasoning, capped at 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, a developer runs clarification on a new feature spec; the Skill identifies that authentication requirements and data retention rules are undefined, asks targeted questions, and records the decisions in the spec. ## Quick Start Run the speckit-clarify skill to review my current feature spec and ask me clarification questions about any ambiguous requirements.

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 into a Clarifications section.

How many clarification questions does speckit-clarify ask?▼

It asks a maximum of 5 questions per session, prioritized by impact and uncertainty. Each question is either multiple-choice with a recommended option or a short answer constrained to 5 words or fewer.

Does speckit-clarify require a spec-kit project structure?▼

Yes, it requires a .specify directory and an existing feature spec created by /speckit-specify. It runs check_prerequisites.py to locate the feature directory and spec file, and aborts if the spec is missing.

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

Run it after /speckit-specify and before /speckit-plan. Skipping clarification is allowed for exploratory spikes, but the skill warns that downstream rework risk increases when ambiguities remain unresolved.

What happens to the requirements checklist after clarification?▼

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