compliance-check

Run post-task governance checks to validate skills usage, documentation updates, and build status. This checklist-based validation ensures artifact completeness, prevents data leakage, and generates a pass/fail report to confirm production readiness.

Post-task governance validation verifies that compliance rules were followed after finishing work. Run it after structural changes, adding automations, modifying packages, or proactively whenever a significant implementation is complete.

Yes, checklist-based compliance checks apply to every major change including package updates and structural changes. They validate skills usage, enforce data cleanliness, and confirm artifact completeness to ensure production readiness.

Run a post-task governance check to validate data cleanliness and artifact completeness. This enforces compliance rules against client data leakage and generates a clear pass/fail report to guide your production release.

Artifact completeness checks fail when required build outputs or documentation updates are missing after modifying automations. Running a post-task governance validation enforces the checklist and generates a report to identify specific failures.

Yes, the compliance validation process generates a clear pass/fail report for production readiness. It verifies governance rules, documentation updates, build success, and artifact completeness to guide your release decisions after major tasks.