speckit-clarify

Identify underspecified areas in feature specs by prompting up to five targeted clarifications.

Updated May 28, 2026

Search Tags:#workflow #specification #requirements #product-management #clarify #spec-verification

Ready to run

npx skills add https://github.com/bdunnette/reaper --skill speckit-clarify-bdunnette

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/bdunnette/reaper/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/bdunnette/reaper --skill speckit-clarify-bdunnette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in a feature specification by prompting up to five targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

Pre-execution checks: detects and loads extension hooks and governance constraints to guide clarification flow.
Structured ambiguity scan: assesses core functional goals, data models, UX flows, non-functional quality attributes, and integration points to surface gaps.
Interactive clarification loop: generates a prioritized list of up to five questions, accepts concise answers, and records decisions directly in the spec.
Spec enrichment: creates a dedicated Clarifications section with daily session tagging and traceable bullets for each accepted answer.
Validation & compliance: optional post-update quality checklist re-evaluates the spec and surfaces outstanding risks.

Quick Start

Identify ambiguities in the feature spec by answering up to five targeted questions and update the spec accordingly.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I identify underspecified areas in a feature specification?▼

You can identify underspecified areas in a feature specification by running a structured ambiguity scan that assesses functional goals, data models, UX flows, and integration points to surface gaps and generate targeted clarification questions.

How do I record clarifications and decisions directly in a spec?▼

You record clarifications and decisions directly in a spec by creating a dedicated Clarifications section with daily session tagging and traceable bullets for each accepted answer during the interactive clarification loop.

What is the best way to update requirements with a prioritized clarification queue?▼

The best way to update requirements with a prioritized clarification queue is to generate up to five targeted questions, accept concise answers, and apply those accepted answers directly back into the spec after each interaction.

Can I validate spec updates against a quality checklist?▼

Yes, you can validate spec updates against an optional post-update quality checklist that re-evaluates the specification and surfaces outstanding risks after applying accepted clarifications.

Does spec clarification work within a spec-kit project structure?▼

Yes, spec clarification works within a spec-kit project structure by detecting and loading extension hooks and governance constraints from the .specify/ directory to guide the clarification flow.