speckit-clarify

Identify underspecified areas in feature specifications and log clarifications.

12|1|Updated Apr 15, 2026

Search Tags:#automation #documentation #collaboration #specification #requirements #clarification

Ready to run

npx skills add https://github.com/reason-healthcare/rh-skills --skill speckit-clarify-reason-healthcare

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature specification and encode clarifications back into the spec to reduce downstream rework during implementation.

Core Features & Use Cases

Structured ambiguity analysis across goals, scope, data model, UX flow, non-functional criteria, and external dependencies.
Incremental clarification: generate up to five targeted questions and record accepted answers in a dedicated Clarifications section, preserving traceability.
Spec-updating automation: apply approved clarifications to the relevant sections of the spec and validate formatting and consistency.

Quick Start

Initiate an interactive clarification session using speckit-clarify to pose up to five targeted questions and update the spec.

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 before implementation?▼

Ambiguities in a feature specification are identified through structured analysis across goals, scope, data models, and non-functional criteria. This targeted clarification process surfaces underspecified areas and logs questions to resolve gaps before development.

How do I track specification clarifications without losing traceability?▼

Specification clarifications are tracked by recording accepted answers in a dedicated Clarifications section. This preserves traceability by automatically applying approved updates directly into the relevant parts of the feature spec.

What is the best way to standardize how specification gaps are captured during grooming?▼

Standardize capturing specification gaps during grooming by enforcing a taxonomy of ambiguity categories. This systematically identifies gaps across data models and dependencies, logging each accepted clarification as a concrete update to the spec.

Can I automatically apply approved clarifications to update an existing spec?▼

Yes, you can automatically apply approved clarifications to update an existing spec. The spec-updating automation validates formatting and consistency while inserting resolved answers into the relevant specification sections.

Does the clarification process limit the number of questions generated per session?▼

Yes, the clarification process limits each incremental session to a maximum of five targeted questions. This constraint ensures focused resolution of underspecified areas before teams move forward with implementation.

What areas of a requirements document should be reviewed for missing details?▼

Review a requirements document for missing details by analyzing goals, scope, data model, UX flow, non-functional criteria, and external dependencies. Structured ambiguity analysis targets these specific areas to surface gaps.