review-coverage

Post-implementation verification is enforced through a residual loop campaign that iteratively checks code-to-spec alignment and regression status until a stable, clean state is achieved.

A residual loop in code review is a finite verification cycle that applies forward-and-reverse checks against original specs and git history, stopping only when the code is proven stable and regressions are eliminated.

You can add review coverage success criteria to project plans by invoking the skill to automatically inject a standardized Review Coverage section that defines verification parameters for the post-ship phase.

Yes, executing iterative review-converge cycles requires integration with host-level goal facilities to manage the verification loop until a stable, clean state is achieved.

Yes, this is designed for regression testing after shipping complex features, orchestrating a rigorous verification loop against git history and original specs to ensure no regressions remain before task completion.

An automated residual campaign is not suited for workflows lacking rigorous code-to-spec alignment requirements or environments without host-level goal facilities to execute the necessary iterative review-converge cycles.