reviewing

Automated code reviews for spec compliance validate implementation diffs against design specifications to ensure feature alignment. This process performs a two-stage evaluation, checking spec compliance first and then code quality, to surface concerns before advancing the development phase.

A two-step code review process evaluates changes in sequential stages: spec compliance and code quality. It reads design and plan documents alongside implementation diffs to validate requirements, producing a structured review artifact that enforces gating decisions before the next development phase.

Validating implementation diffs against a design document requires a context-aware assessment that reads design.md and plan.md files. The review process compares these specifications directly against the code changes to confirm the completed feature aligns with the original defined requirements.

Generating a review artifact documents all quality check findings and resolutions within a dedicated markdown file. This artifact updates the feature state and enforces gating decisions, ensuring no development phase advances without passing both spec compliance and code quality validation.

Automated code quality checks should be used during the review phase of feature development before integration. Applying these checks across design, plan, and diff artifacts reduces defects early and ensures the implementation meets quality standards before advancing the workflow.