review-implementation

Spec-to-code comparison extracts requirements into a flat checklist and classifies each item as done, partial, missing, or diverged. This tracks completion state and generates a report highlighting any gaps between implementation and requirements.

Checking code completion status involves extracting all requirements into a flat checklist and verifying each item against the code. You classify requirements as met, partially met, not met, or divergent to identify gaps and track overall completion state.

The best way to identify missing requirements is generating a flat checklist from the specification and classifying each item as done, partial, missing, or diverged. This highlights gaps between the plan and the actual code implementation.

Yes, spec-to-code comparison requires manual input for locating the specification and creating the checklist. You must provide the plan or requirements doc so the review can extract requirements and classify implementation status accurately.

A code review checklist extracts all requirements from a specification into a flat list to track completion. It verifies the code by classifying each item as met, partially met, not met, or divergent, producing a detailed alignment report.