speckit-clarify

To identify missing requirements in a feature specification, this Skill analyzes the spec and asks up to five targeted multiple-choice or short-answer questions. It detects vague acceptance criteria and encodes the answers directly back into the document.

The best way to clarify vague acceptance criteria is to prompt with focused questions and merge responses into a new Clarifications section. This approach preserves an auditable session history under a per-session timeline to support planning and validation.

You update a spec file with clarification answers by applying this Skill to specs following the .specify workflow. It validates consistency and saves the document after every accepted answer, adding a new Clarifications section with a daily session subheading.

Yes, this spec clarification tool works directly with existing .specify workflows. It applies to specs that follow this structure and updates them by creating a new Clarifications section containing a daily session subheading for traceable decision-making.

The tool generates up to five clarification questions per spec session. These questions are highly targeted, answerable with two to five multiple-choice options or short answers, and are designed to identify underspecified areas in the feature specification.

You should avoid automated clarification when your spec does not follow the .specify workflow or lacks underspecified areas. The tool targets unclear actor roles and missing requirements, so fully detailed specs will not benefit from the questioning process.