speckit-clarify

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill speckit-clarify-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/360org/vuaassistant/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/360org/vuaassistant --skill speckit-clarify-360org

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 development begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories (functional scope, data model, UX flows, 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, with recommended multiple-choice options or suggested short answers. - Incremental Spec Updates: Writes each accepted answer into a ## Clarifications session section and updates the relevant spec sections, 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, data constraints, and acceptance criteria so the plan is built on firm requirements. ## 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 speckit-clarify skill in a spec-kit project. It scans the active 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 the spec-kit workflow?▼

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

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory. It runs check-prerequisites.sh to locate the feature spec and optionally loads .specify/memory/constitution.md for project principles.

How many clarification questions does the skill ask?▼

It 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 5 words or fewer.

What happens if the spec has no ambiguities?▼

The skill reports that no critical ambiguities were detected, outputs a compact coverage summary showing all categories as Clear, and suggests proceeding to the planning phase.