user-validate

Standardizing artifact approval workflows requires a single canonical validation gate that maps decisions into structured approve, changes-requested, or rejected outcomes. This prevents workflows from reimplementing validation logic differently across various checkpoints.

Workflow gate validation handles unavailable backend services by using backend-aware fallback execution, defaulting to an internal structured prompt to produce a consistent approval, changes-requested, or rejection outcome without looping.

The best way to structure user sign-off for spec reviews and plan approvals is applying a consistent validation protocol that resolves user-gate validation into a single structured outcome before a lifecycle stage continues.

User gate validation does not support automatic retries. It enforces strict decision mapping without in-skill retry loops, ensuring a clean changes-requested outcome is returned for the workflow to handle externally.

Yes, you can use the plannotator review backend for artifact validation checkpoints. The validation flow is backend-aware and will use the optional plannotator backend when available, or fall back to a default internal structured prompt.

You need a structured validation protocol for workflow checkpoints when a lifecycle stage finishes drafting an artifact, such as a proposal or spec, and requires a clean user decision to approve, reject, or request changes before proceeding.