skills.rest
ericstiles
ericstilesCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Detect underspecified areas in feature specifications and capture clarification questions.

Updated Apr 9, 2026
Search Tags:#specification#requirements#ambiguity#spec#session#clarify
One-click install
npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-clarify-ericstiles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/ericstiles/spec-kit-backlog/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-clarify-ericstiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in feature specifications slows down planning and increases rework. speckit-clarify identifies underspecified areas and drives precise clarifications that tighten the spec before planning.

Core Features & Use Cases

  • Detects gaps across functional scope, data model, UX interactions, and non-functional criteria.
  • Generates up to five highly targeted clarification questions and records answers back into the spec.
  • Automates integration with the spec-kit workflow to keep the active specification aligned with implementation plans.

Quick Start

Start a clarification session against the active feature spec by running /speckit.clarify.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify ambiguity in a feature specification before planning?▼

Identifying ambiguity in a feature specification involves detecting underspecified areas across functional scope, data models, and UX interactions. This clarification process tightens the spec and reduces rework before planning.

How do I run a clarification session for my project spec?▼

You can run a clarification session by starting the workflow against your active feature spec. The session generates up to five targeted questions to capture precise answers that are recorded directly back into the specification.

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

The spec clarification workflow requires a spec-kit project structure containing a .specify directory. This environment supports the clarification workflow and enables automatic updates to the active specification.

What is the maximum number of clarification questions generated per session?▼

The maximum number of targeted clarification questions generated per session is five. This limit ensures structured ambiguity detection and session-based clarification management without overwhelming the specification review.

What types of gaps should I look for when clarifying feature requirements?▼

When clarifying feature requirements, look for gaps across functional scope, data model definitions, UX interactions, and non-functional criteria. Detecting these areas ensures precise clarifications that align the spec with implementation plans.

Can I automatically update my feature spec with clarification answers?▼

Yes, you can automatically update your feature spec with clarification answers. The workflow records answers back into the spec and automates integration to keep the active specification aligned with implementation plans.

Related Skills

Explore More Product & Management Skills→
KamiJeongKamiJeong

speckit-clarify

Identify and resolve ambiguities in active feature specifications before implementation planning.

Community
Intermediate
shaman007shaman007
25

speckit-clarify

Identify and resolve ambiguities in feature specifications through structured questioning.

Community
Advanced
thktthkt
11

validating-specs

Validate consistency and traceability between SOW and Spec documents.

Community
Advanced
Pacheco95Pacheco95

speckit-clarify

Identify underspecified areas in feature specifications and encode clarifications into structured updates.

Community
Advanced