clarify

Lock requirements by running a structured, round-based Q&A session that extracts ambiguities from research artifacts and transforms them into locked acceptance criteria and scope boundaries. This prevents ambiguous inputs from propagating into planning.

Capturing non-functional constraints and out-of-scope boundaries is best achieved through a structured clarification process that logs decisions and generates a compact artifact. This ensures downstream stages rely on consistent scope and success criteria.

Run a structured requirements clarification session by providing the research artifact slug or path. This triggers a 2-round interview flow with pre-filled defaults to reduce back-and-forth and produce a compact artifact for downstream stages.

Yes, you can use clarification to generate artifacts for downstream stages like TestPlan and PlanReview. It satisfies workflow rules for decision logging and artifact generation, ensuring consistent scope and success criteria across decomposition and planning.

You do not strictly need a completed research artifact before locking acceptance criteria, as clarification can be invoked standalone. However, triggering it after research allows it to extract ambiguities and pre-fill defaults for a more efficient Q&A flow.