speckit-clarify

Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-clarify-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-clarify
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-clarify-omkar-code-mur

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 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 Clarification Loop: Asks up to 5 high-impact questions one at a time, each with a recommended option or suggested answer, and writes accepted answers into a ## Clarifications section of the spec. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates, toggling checkbox states and reporting 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 firm requirements. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to find 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 before planning?

Run the speckit-clarify workflow on the active feature spec. 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 directly into the spec file.

What is the speckit-clarify command in spec-kit?

It is a clarification workflow that runs between /speckit-specify and /speckit-plan. It identifies underspecified areas in the current feature spec, asks focused questions with recommended options, and encodes the answers back into the spec under a Clarifications section.

Does speckit-clarify require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory. It runs check-prerequisites.ps1 to locate the feature spec, optionally loads .specify/memory/constitution.md, and reads extension hooks from .specify/extensions.yml if present.

How many clarification questions can be asked in one session?

A maximum of 5 questions per session. Each question must be answerable with a multiple-choice selection of 2-5 options or a short answer of 5 words or fewer, and retries for the same question do not count against the quota.

What happens to the requirements checklist after clarification?

If FEATURE_DIR/checklists/requirements.md exists, each checkbox item is re-evaluated against the updated spec. Markers toggle only when pass/fail state changes, and the completion report shows before/after pass counts plus newly passing items and regressions.