human-qa-loop

To enforce human review on planning drafts, you wrap your draft sections and explicit success criteria in a loop that iterates with the user until all criteria are explicitly validated. The workflow asks only for missing information to gate completion.

Disposition gating in workflow automation is a human review mode that enforces explicit Accept, Reject, or Defer decisions for each finding in a planning review. This prevents loosely validated work from advancing until every item receives a formal disposition.

You validate success criteria during draft iteration by applying a criteria validation loop that checks the target draft against explicit requirements. It asks targeted confirmation questions and filters for human-agency items, avoiding unnecessary churn while preserving required output contract fields.

Yes, the human-qa-loop requires preserving specific output contract fields including DraftSection, Checklist, Questions, and Notes. The framework maintains this ordering and returns N/A for any fields that are not applicable to the current planning or review context.

Yes, you can use comprehension mode to confirm problem definition by asking targeted confirmation questions. This mode validates user understanding of the draft, while disposition mode handles Accept/Reject/Defer decisions and default mode manages general clarification.

The best way to prevent advancing incomplete planning work is to apply an iterative user loop that requires explicit success criteria satisfaction before stopping. This ensures problem definitions and technical plans are fully validated through human-agency filtering and criteria checks.