skill-staged-review

Spec compliance is enforced by loading an intent contract to validate success criteria and boundary checks before progressing to a full code quality review. This two-stage process ensures features meet intended goals before merging.

A two-stage review process separates spec compliance validation from code quality checks to ensure features meet goals and pass rigorous gates. Stage 1 validates intent contracts, while Stage 2 performs full quality and stub detection.

Code quality and stub detection are checked during the second stage of a staged review, which validates architecture, error handling, security, performance, readability, and test coverage before merge readiness is determined.

If no intent contract exists, the staged review process warns the user and proceeds directly to Stage 2 code quality checks. This fallback ensures code quality validation still occurs even without explicit spec compliance criteria.

Staged review is applicable to major feature work, pull request preparation, or any scenario requiring staged validation. Gate-based decisioning ensures both spec compliance and quality stages pass before progression.

A staged review reports nothing to review when no changes are detected on the feature branch. This ensures the validation process only triggers gate-based decisioning when actual code modifications exist to assess.