quality-gate

Multi-pass quality gating automates layered reviews to verify deliverables are complete and compliant. It applies rotating self-review lenses, domain reviews, and fresh-context verification to catch correctness, robustness, and architecture issues.

Fresh-context verification is a Layer 2 review mechanism where subagents validate the final deliverable state independently. This prevents anchoring bias and ensures thorough validation without being influenced by prior review context.

Yes, automated quality gates apply to code changes, research artifacts, planning outputs, and other significant project deliverables. The workflow enforces lifecycle, memory, and artifact gates to ensure traceability and plan adherence across domains.

Domain reviews function as a Layer 1.5 step between self-review and fresh-context verification. They target domain-specific compliance and quality issues, surfacing problems that general self-review lenses might miss before final gating.

Self-review alone risks anchoring bias, where the reviewer's assumptions carry through all passes. Without Layer 2 fresh-context subagents verifying the final state, subtle completeness and compliance gaps can remain undetected before delivery.

No external dependencies are required. The workflow aligns with the Skill's frontmatter governance and enables optional script, reference, or asset resources when present, supporting gatekeeping for lifecycle, memory, and artifact traceability natively.