speckit-clarify

Identify underspecified areas in feature specs and encode clarification answers back into the spec.

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-clarify-esri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-clarify
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-clarify-esri

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 underspecified areas in a spec 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 integrates accepted answers directly into the spec file under a Clarifications section. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates and reports newly passing items, regressions, and outstanding gaps. - Use Case: Before running implementation planning on a new feature, run this Skill to resolve open questions about security posture, scale targets, and edge-case handling so downstream plans are built on confirmed decisions. ## 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?

Run the speckit-clarify workflow on the active feature spec. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the accepted answers back into the spec file.

When should I run spec clarification in spec-kit?

Run clarification after creating the spec with speckit-specify and before running speckit-plan. Resolving ambiguities first reduces downstream rework risk in planning, task decomposition, and acceptance test design.

What project structure does speckit-clarify require?

It requires a spec-kit project with a .specify directory and an active feature spec located via the check-prerequisites script. If the spec file is missing, you must run speckit-specify first.

How many clarification questions does the workflow ask?

The workflow 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 clarification update the requirements checklist automatically?

Yes. If a requirements.md checklist exists in the feature directory, the workflow re-evaluates each checkbox against the updated spec, toggles only items whose pass state changed, and reports newly passing items and regressions.