speckit-clarify

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

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-clarify-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-clarify-narenkarthikbm

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 detects those gaps and resolves them through targeted questions before any planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories (functional scope, data model, non-functional requirements, edge cases, terminology) and marks 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 based on best practices. - Incremental Spec Integration: Writes each accepted answer directly into the spec under a Clarifications section and updates the relevant requirement sections, then re-validates the spec quality checklist. - Use Case: After drafting a spec with /speckit-specify, run this Skill to resolve open questions about authentication, scale targets, and edge cases before handing the spec to /speckit-plan. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and resolve its ambiguities.

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 edge cases, then asks up to 5 targeted questions and writes the answers back into the spec file.

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

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

Does speckit-clarify require a specific project structure?

Yes, it requires a spec-kit initialized project with a .specify directory and an existing feature spec. If no spec exists, it instructs you to run /speckit-specify first rather than creating one.

How many clarification questions does the skill 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 five words or fewer.

What happens to the spec quality checklist after clarification?

If FEATURE_DIR/checklists/requirements.md exists, the skill re-evaluates each checkbox against the updated spec, toggles only markers whose state changed, and reports before/after pass counts including regressions.