technical-review

To verify implementation against acceptance criteria before a pull request, you trigger a task-based assessment using the latest plan and optional specification to generate actionable, structured feedback.

Checking if every plan task is implemented and tested correctly requires a comprehensive plan verification process that evaluates implementation scope, tests, and code quality to produce structured approve or request changes guidance.

Technical review does work without a full specification document, as it primarily relies on the latest plan to verify implementation scope and code quality, using the optional specification to enhance the assessment.

You can use plan verification as a standalone contract entry to validate finished work, or sequentially after implementation, to rigorously assess code changes against defined plans and quality standards.

From a quality gate review, you should expect structured feedback such as clear guidance to approve, request changes, or provide comments with rationale based on the evaluation of acceptance criteria and code quality.

You should not use automated code quality assessment when a defined plan or task list is absent, because the review mechanism relies on comparing implemented work against original plan tasks and acceptance criteria to generate feedback.