iikit-02-clarify

Clarify specs by scanning them for underspecified areas and generating targeted questions that surface gaps in goals, data, UX, and non-functional attributes. This reduces rework downstream by capturing answers directly into a structured Clarifications section.

Use ambiguity detection to prioritize up to 5 clarifying questions ranked by impact. Answer one question at a time and append responses to your spec with dated session notes, ensuring requirements stay synchronized as you resolve uncertainties.

Run the clarify workflow after your feature spec exists, answer each question in sequence, and the Clarifications section automatically updates with session notes and final answers, maintaining a complete audit trail of requirement refinements.

Yes. Ambiguity detection scans across goals, data, UX, non-functional attributes, and governance constraints, surfacing gaps you might miss in initial drafts and ensuring compliance requirements are explicit before implementation.

Run the clarify workflow immediately after drafting a feature spec to surface underspecified areas early. One-question-at-a-time loops let you resolve ambiguities incrementally without overwhelming stakeholders or blocking downstream planning.

The workflow prioritizes up to 5 questions by impact and scope. Complete the first session, then run clarify again on the updated spec to surface and prioritize the next set of gaps until your specification is sufficiently detailed.