skill-staged-review

A staged review validates software changes by separating specification validation from code quality review. It checks intent contracts and success criteria first, then analyzes architecture, security, and performance to ensure teams build the right feature before optimizing implementation.

A staged code review separates specification validation from implementation quality analysis. It first validates intent contracts and success criteria, then reviews architecture, security, error handling, performance, and testing to prevent incomplete or misaligned feature deliveries.

Detect stub implementations by applying a multi-factor quality assessment that scans for potential stubs alongside architecture, security, error handling, performance, readability, and testing checks. This ensures incomplete code blocks are caught before merging.

Yes, you can coordinate multi-provider reviews for major software features. The staged review process validates intent contracts first, then coordinates detailed code quality analysis across multiple providers to ensure comprehensive engineering review before shipping.

You need spec validation before code quality review when a major feature is complete or a pull request is ready. Validating requirements first ensures teams build the right thing before optimizing how it is built, preventing misaligned feature deliveries.