speckit-clarify

To resolve ambiguities in a feature specification, run a structured clarification flow that scans for functional, data, and edge-case gaps, then generates up to five high-impact questions to produce concise, testable answers. This prevents downstream architecture churn.

Finding missing decisions in a spec file involves performing a structured ambiguity scan across categories like security, data models, and non-functional requirements. This process marks the status of each category and prioritizes questions that materially reduce rework risk.

You update a markdown specification file by applying incremental, atomic edits that integrate each accepted answer immediately. This approach preserves the existing markdown structure while ensuring newly added acceptance criteria remain testable.

Yes, spec clarification works directly with Spec Kit projects that include a .specify directory. The process executes prerequisite checks during pre-planning sessions to validate the environment before generating constrained multiple-choice or short-answer questions.

You need to run a clarification session for your requirements during the pre-planning phase. Running it early surfaces integration, terminology, and edge-case gaps that would otherwise cause architecture churn and untested scenarios.