phase-complete

Verify phase completion by running a deterministic checklist that validates code presence, test success, lint and type checks, build status, and PR readiness. It outputs a clear pass or fail result with traceable remediation steps for any blockers found.

A deterministic phase gate checklist is an automated validation process ensuring a development phase meets all closure criteria. It prevents premature completion by enforcing code, tests, linting, builds, and pull request readiness before reporting a final pass or fail status.

Yes, automated quality checks apply to software engineering workflows across both backend and frontend repositories. The process validates phase gates, code completeness, test success, type validity, and integration readiness uniformly across different project environments.

Validate integration readiness by running a phase closure workflow that checks code, tests, lint, type validity, and build status. It confirms all gates are satisfied and reports any blockers to the team to prevent marking the phase complete prematurely.

Report code quality blockers by running an automated phase completion workflow that outputs a clear pass or fail result. It provides traceable remediation steps for failed criteria including tests, linting, builds, and pull request readiness for the team to address.

Phase completion with failing checks occurs when closure criteria are not strictly enforced. A deterministic checklist prevents this by validating lint and type checks, test success, and build status, ensuring the phase fails and provides remediation steps before proceeding.