speckit-clarify

Generate clarifying questions and record answers into feature specifications.

Updated Aug 23, 2026

Search Tags:#planning #specification #requirements #clarification #interaction #feature

Ready to run

npx skills add https://github.com/jacobbweber/Zerto-PS-Admin-SDD --skill speckit-clarify-jacobbweber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/jacobbweber/Zerto-PS-Admin-SDD/tree/main/.agent/skills/speckit-clarify
Command: npx skills add https://github.com/jacobbweber/Zerto-PS-Admin-SDD --skill speckit-clarify-jacobbweber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature specification by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

Structured ambiguity scanning across functional scope, domain data model, UX flow, error handling, and non-functional criteria.
Generates up to five targeted clarification questions to surface missing decisions and reduce downstream rework.
Applies accepted answers to the spec and records a traceable clarification log for auditing and planning.

Quick Start

Run the speckit clarify workflow to identify ambiguities in the active feature spec and update the spec with accepted clarifications.

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify ambiguities in a feature specification?▼

To identify ambiguities in a feature specification, generate up to five targeted clarifying questions that scan functional scope, data models, UX flow, and non-functional criteria to surface missing decisions and reduce downstream rework.

How do I resolve underspecified areas in a feature spec and record the decisions?▼

Resolve underspecified areas by applying accepted answers directly into the feature spec and recording a traceable clarification log, ensuring structured ambiguity management and traceable decision logging for auditing and downstream planning.

Does the spec clarification workflow require a specific project directory structure?▼

Yes, the spec clarification workflow applies to active feature specs within a project structure that contains a .specify directory, ensuring alignment with downstream planning through formalized acceptance criteria and measurable outcomes.

What aspects of a specification should I clarify to ensure traceable decision logging?▼

Clarify functional scope, domain data models, UX flow, error handling, and non-functional criteria to ensure traceable decision logging. This structured ambiguity scanning formalizes acceptance criteria and measurable outcomes for downstream planning.

Can I limit the number of clarifying questions generated for my feature spec?▼

Yes, the specification clarification process generates a maximum of five targeted clarification questions to surface missing decisions efficiently, applying accepted answers to the spec and recording a traceable clarification log for auditing.