speckit-clarify

Detects underspecified areas in feature specs and records targeted clarification answers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguous requirements, missing decisions, and vague language that cause rework during planning and implementation. This Skill systematically scans a spec-kit feature spec, identifies gaps, and resolves them through up to 5 targeted clarification questions whose answers are written directly back into the spec file. ## 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, constraints, and terminology. - Interactive Questioning Loop: Asks one question at a time (maximum 5) with recommended multiple-choice options or suggested short answers, each grounded in best practices. - Incremental Spec Updates: Appends each accepted answer to a ## Clarifications session section and updates the relevant spec sections atomically after every answer. - Use Case: Before running /speckit.plan, a developer invokes this Skill on a new feature spec; it detects that security posture and scale assumptions are undefined, asks two focused questions, and records the answers as measurable criteria in the spec. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to 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 spec-kit feature specification?

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

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

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

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.

What happens if the feature spec file is missing?

The workflow aborts and instructs you to run /speckit.specify first. It does not create a new spec file, since clarification only operates on an existing feature specification in the .specify project structure.

Where are clarification answers recorded in the spec?

Accepted answers are appended as Q&A bullets under a ## Clarifications section with a dated session subheading, and the relevant spec sections such as Functional Requirements or Success Criteria are updated to reflect each answer.