quality-gates

Approval gates are checkpoints that require user validation before a workflow advances. Configure explicit approval gates in your plan, set a maximum iteration cap, run the workflow, and prompt users for final validation at each gate to ensure quality thresholds are met before proceeding to the next stage.

Iterative refinement automates repeated cycles until quality reaches a threshold. Define exit criteria and iteration limits in your workflow configuration, then the system automatically refines output based on feedback until stopping conditions are met or the cap is reached.

Yes. Severity classification categorizes findings as CRITICAL, HIGH, MEDIUM, or LOW to prioritize fixes and guide multi-agent decisions. This enables consensus patterns where multiple reviewers focus effort on high-impact issues before lower-priority ones.

Cost and quality gates are approval checkpoints that validate resource spend and quality metrics before deployment. Configure these as approval-driven gates with audit logging and user prompts to ensure compliance and user alignment before advancing through deployment stages.

No, but approval gates support TDD-driven loops as an option. You can configure them for any approval-driven, iterative, or feedback-loop workflow across design, development, testing, and deployment—TDD is one supported pattern among many.

Iteration caps prevent infinite refinement loops by setting a hard limit on cycles. Once the cap is reached, the workflow exits regardless of whether quality thresholds are met, so set caps conservatively to balance thoroughness against cost and time constraints.