speckit-clarify

To clarify ambiguous feature specifications, you can use a structured ambiguity scan that evaluates functional, data model, UX, and edge case categories. It asks up to five targeted questions and writes accepted answers directly back into the spec file.

The best way to reduce ambiguity in user stories is through an interactive question loop that enforces short responses or multiple-choice options. This minimizes misinterpretation and incrementally updates the spec sections after each accepted answer.

QA acceptance criteria are added by scanning the spec for acceptance signals and missing decisions, then prompting for targeted clarifications. Accepted answers are persistently written into a designated clarifications section within the feature spec.

Spec clarification supports optional pre-hook execution by reading project hooks from .specify/extensions.yml. It runs configured hooks before the clarification process begins, allowing custom pre-processing within the spec-kit workflow.

Prerequisites are validated using .specify/scripts/powershell/check-prerequisites.ps1. This script ensures the required environment and configuration dependencies are met before the agent begins scanning the current feature spec.

Yes, the spec clarification process enforces strict question limits, asking exactly one question at a time up to a maximum of five targeted questions to resolve underspecified features without overwhelming the user.