speckit-superb-verify

To enforce fresh verification evidence before completion, apply a mandatory verification gate against the current implementation. This validates completion claims by requiring fresh test evidence and a spec-coverage checklist before finalizing.

A completion gate in speck kit workflows is a mandatory post-hook that intercepts completion claims. It applies a built-in verification baseline to ensure no implementation finalizes without passing fresh test and evidence validation.

Validate test coverage and evidence by running a spec-kit driven checklist against the current implementation. This generates a structured completion report that gates the final completion claim until all evidence is verified.

Yes, the speckit verification gate works without remote access by using multi-source skill loading. It attempts local plugin loading first, then remote fetch, and finally relies on an embedded fallback to guarantee a verification baseline is always available.

You need to use a verification gate for quality assurance when finalizing implementation tasks within speck kit workflows. It acts as a mandatory post-hook to ensure claims are backed by fresh verification evidence and spec-coverage validation.