11-verify-impl

Verify implementation completeness by running a verification process that checks feature-level alignment against the product plan, collecting results from QA and E2E tests to ensure the build matches user intent.

Feature-level completeness checking is the process of validating that each implemented feature meets the required criteria from the product plan. You need it after QA and E2E tests are completed to approve features before deployment.

Validate project implementation alignment by checking the build against user journeys and the product plan, collecting QA and E2E test results to confirm the final output matches the intended user outcome.

Yes, implementation verification requires QA and E2E reports, a feature list, and user journeys as inputs to operate effectively and provide targeted patches for flagged issues.

To get targeted patches for flagged issues, walk through the feature approval process during implementation verification, which checks feature areas against the product plan and generates fixes for any identified problems.

The best way to approve features before deployment is to run a post-test verification skill that walks you through each feature area, checking completeness against the product plan and providing targeted patches for flagged issues.