speckit-clarify

Spec ambiguity resolution involves scanning a feature spec for unclear scope, interfaces, and runtime behavior, then writing confirmed clarifications back into spec.md. This process requires prerequisite gating and human review of high-impact gaps before proceeding to the next stage.

Spec-kit workflow routing directs clarified spec.md sections to the appropriate development stage after ambiguity review. It identifies underspecified capability areas, establishes validation targets and compatibility decisions, and routes the updated document forward for planning or implementation.

Review a draft feature spec by scanning for unclear ownership, module boundaries, runtime behavior, and rollout risk. The process asks concise human-reviewed questions only when high-impact gaps exist, ensuring material changes to behavior or interfaces are resolved before planning begins.

Human review during spec clarification is needed when high-impact gaps exist that would materially change behavior, rollout risk, or module boundaries. It targets only blocking ambiguities in scope, validation, UI parity, and compatibility rather than minor underspecified details.

Yes, you can update spec.md directly with confirmed clarifications and next-stage routing. The process writes reviewed answers back into the document so it can stand alone for downstream planning, ensuring module boundaries, interfaces, and runtime behaviors are fully specified.

Spec clarification works for UI parity and rollout risk assessment by identifying underspecified capability areas in these domains. It scans the feature spec for unclear validation targets and compatibility risks, generating human-reviewed questions to resolve blocking ambiguities before implementation.