wz:verification

Task completion verification requires fresh command evidence or a deterministic proof path to ensure integrity. This skill enforces canonical verification gates and guides collection of reproducible proof artifacts using a standardized workflow before sign-off.

Automated evidence collection for project governance sign-off uses a proof-collector mechanism to gather verifiable artifacts. This ensures reproducibility and traceability by enforcing that every completion claim is backed by deterministic proof paths before closure.

Verification gates for QA workflows are set up by following standardized guidelines and collecting fresh evidence using a proof-collector. This structured proof-collection workflow ensures reproducibility and verifiable validation before marking a task complete.

Deterministic proof paths for task closure workflows are needed when verifiable proofs are required before sign-off. They ensure integrity and traceability in software development, project governance, and quality assurance by backing every completion claim with fresh command evidence.

Yes, this verification workflow applies to software development, project governance, and QA workflows. It enforces canonical verification gates and integrates automated evidence gathering to enable verifiable sign-off across these domains requiring verifiable validation.

Task verification requires fresh command evidence to ensure integrity and traceability. Historical logs lack the deterministic proof path necessary to guarantee reproducibility, whereas fresh evidence validates that every completion claim is currently accurate before sign-off.