sdcorejs-verify-before-done

Verifying acceptance criteria before shipping involves loading the spec's criteria and running build, lint, full tests, and stack-appropriate checks. Completion is blocked until every criterion is verified or explicitly deferred by the user.

Spec compliance verification is a process that prevents an agent from marking a feature complete by running criterion-by-criterion checks. It ensures the coded feature matches the spec before auto-docs generation, commits, or PR creation.

Yes, acceptance criteria verification applies to Angular Portal, NestJS, and NextJS code-writing workflows. It runs stack-specific checks, including NextJS-specific i18n, content, and SEO checks, before allowing a feature to be handed off.

To enforce CI quality gates and smoke testing before a pull request, run a mandatory verification process that triggers automatically before commits and PRs. This enforces a verify-then-hand-off rule by running build, lint, and full tests.

If an acceptance criterion fails during feature verification, the system blocks the done status and refuses to mark completion. The feature cannot proceed to auto-docs or commits until the criterion is fully verified or explicitly deferred.

You need to run automated acceptance criteria checks when unit tests pass but the feature must match user requirements. This prevents incomplete work by applying spec-driven verification modes like E2E route probes and stack smoke checks before shipping.