sweep-verification

Enforce fresh verification evidence before declaring artifact completion.

71|9|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/kucherenko/gangsta --skill sweep-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sweep-verification
Source: https://github.com/kucherenko/gangsta/tree/main/skills/sweep-verification
Command: npx skills add https://github.com/kucherenko/gangsta --skill sweep-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule prevents premature completion by insisting on fresh verification evidence before declaring work done, reducing defects and rework.

Core Features & Use Cases

  • Enforces a formal verification step before artifact completion.
  • Captures, records, and references evidence to support status claims.
  • Integrates into development and release workflows for auditable quality control.

Quick Start

Run the verification workflow to generate fresh evidence and confirm completion.

Frequently Asked Questions about sweep-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce verification evidence before declaring a development task complete?

Verification evidence prevents premature completion by requiring fresh proof before closure. You enforce a defined verification command, capture the output as evidence, and validate it against auditable pass criteria to reduce defects and rework.

What is verification evidence in software release workflows?

Verification evidence is fresh, captured proof generated by a formal verification command. It supports completion claims in development and release workflows by providing auditable quality control before an artifact is marked done.

How do I automate claim validation for testing artifacts?

Automate claim validation by running a verification workflow that executes a defined command and reads the resulting evidence. This enforces auditable pass criteria, ensuring every completion claim is backed by fresh verification data.

Do I need specific testing frameworks to require verification evidence?

No specific testing frameworks are required. The verification process enforces a defined verification command and reads evidence directly, allowing integration into existing development and release workflows without strict framework dependencies.

What is the best way to prevent premature completion claims in development?

The best way to prevent premature completion is enforcing a formal verification step that captures fresh evidence. By requiring this proof before closure, you reduce defects and rework while maintaining auditable quality control.