speckit-clarify

To reduce specification ambiguity before planning, this Skill scans your active spec for missing decisions across functional, non-functional, UX, and data categories, then interactively prompts you for targeted answers to resolve underspecified areas.

You can update a spec-kit feature specification incrementally by answering the interactive clarification prompts; the Skill records your accepted answers into the appropriate spec sections and saves after each integration to minimize rework risk.

Yes, spec clarification supports optional and mandatory pre-clarification hooks configured via .specify/extensions.yml, allowing you to execute custom extension logic before the ambiguity scanning process begins.

The maximum number of clarification questions asked for a feature spec is five. The Skill limits questioning to high-impact areas using constrained answer formats to efficiently resolve underspecified requirements.

Yes, you need prerequisite path checks via check-prerequisites.ps1 before resolving spec ambiguity. The Skill validates your environment paths to ensure the active spec-kit project is correctly configured before clarification.

You should not use automated spec clarification if your feature specification is already implementation-ready or if your project lacks the required spec-kit structure and prerequisite path configurations needed for validation.