speckit-clarify

Identify and resolve ambiguities in feature specifications through targeted clarification questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and unresolved ambiguities that cause rework during planning and implementation. This Skill systematically scans a spec for underspecified areas and encodes clarified answers directly back into the spec file. ## 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. - Interactive Questioning Loop: Asks up to 5 high-impact clarification questions one at a time, each with a recommended option or suggested answer. - Incremental Spec Updates: Writes each accepted answer into a Clarifications section and updates the relevant spec sections atomically, 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 targets, and edge-case handling 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 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 feature specification?

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

When should I run spec clarification in spec-kit?

Run clarification after speckit-specify and before speckit-plan. Resolving ambiguities at this stage reduces downstream rework, since planning and task decomposition depend on confirmed requirements.

How many clarification questions does the workflow ask?

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

Does spec clarification require the spec-kit project structure?

Yes, it requires a spec-kit project with a .specify directory and an existing feature spec created by speckit-specify. If the spec file is missing, the workflow instructs you to run speckit-specify first.

What happens to the requirements checklist after clarification?

If a requirements.md checklist exists in the feature directory, it is re-validated against the updated spec. Checkbox states are toggled only when items newly pass or regress, and the completion report shows before and after pass counts.