ai-factory.verify

You can verify task completion by running a comprehensive post-implementation audit that compares the codebase against your defined plan. This process validates build compilation, test execution, and linting while identifying any deviations or incomplete implementations.

Post-implementation code auditing is a verification process that detects drift between project specifications and the actual code. You need it after completing a feature to check for lingering artifacts, undocumented environment variables, and configuration consistency before deployment.

Yes, you can enable strict mode to enforce pre-merge quality gates in your CI/CD pipeline. This mode ensures all build, test, and lint checks pass while verifying that no planned tasks or requirements are missed before merging code.

Check for leftover artifacts and undocumented environment variables by running a consistency verification audit. This process scans the implementation to detect configuration inconsistencies, lingering TODO comments, and any drift from the original project specifications.

The best way to detect plan drift is to perform an automated consistency verification that compares the implemented code against the original plan. This identifies deviations, incomplete implementations, and configuration inconsistencies to ensure strict adherence to project specifications.