speckit-clarify

Generate targeted clarifications for feature specifications and encode answers into the spec.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/william-menezes/pet-volta --skill speckit-clarify-william-menezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/william-menezes/pet-volta/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/william-menezes/pet-volta --skill speckit-clarify-william-menezes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in a feature specification by generating up to five highly targeted clarifications and encoding answers back into the spec to reduce rework.

Core Features & Use Cases

  • Proactive gap discovery across functional, data, UX, performance, and compliance dimensions.
  • Session-based clarifications organized under a dedicated Clarifications section with a date.
  • Automated, testable updates to the spec that normalize terminology and remove ambiguities.

Quick Start

Provide the active feature spec to begin the clarification session.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify gaps in my feature specification before development starts?

You can identify specification gaps by generating up to five targeted clarifications across functional, data, UX, non-functional, integration, edge-case, and constraint dimensions to proactively discover underspecified areas and reduce rework.

What is the best way to update a requirements document with new clarifications?

The best way to update requirements is to append dated session entries under a dedicated Clarifications section and apply resolutions directly to relevant spec sections, which normalizes terminology and removes ambiguities automatically.

Can I encode clarification answers directly into an existing feature spec?

Yes, you can encode clarification answers back into an existing feature spec by applying resolutions to relevant sections after each accepted answer, which ensures the specification stays testable and removes ambiguities.

How many clarification questions should I generate for a software requirement?

You should generate up to five highly targeted clarification questions for a software requirement, applying a taxonomy that covers functional, data, UX, non-functional, integration, edge-case, and constraint aspects to surface gaps.

Does spec clarification work for non-functional and compliance requirements?

Yes, spec clarification works for non-functional and compliance requirements by applying a taxonomy that explicitly covers non-functional, constraint, and edge-case dimensions to surface gaps and drive concrete questions within the specification.