verification-before-completion

Enforce fresh verification evidence before declaring completion in software workflows.

2|Updated Feb 7, 2026

Search Tags:#verification #compliance #evidence #quality-assurance #code-review #continuous-integration

Ready to run

npx skills add https://github.com/SamuelJennings/django-mvp --skill verification-before-completion-samueljennings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/SamuelJennings/django-mvp/tree/main/.github/skills/verification-before-completion
Command: npx skills add https://github.com/SamuelJennings/django-mvp --skill verification-before-completion-samueljennings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature completion claims by requiring fresh verification evidence before any success statements.

Core Features & Use Cases

Enforces evidence-based completion: requires running verification steps and capturing outputs before claiming success.
Guides teams on where and how to verify work (tests, builds, lint, etc.) and how to report results.
Use Case: before submitting a PR, trigger verification to attach verifiable results showing all checks pass.

Quick Start

Run the full verification workflow and attach its fresh output to justify any completion claim.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I prevent premature completion claims in software development workflows?▼

You prevent premature completion claims by enforcing verifiable evidence before declaring success. This requires running verification commands, capturing fresh outputs, evaluating results, and reporting decisions only when evidence supports them.

How do I attach verifiable verification results to a pull request?▼

To attach verifiable results to a pull request, trigger the verification workflow to run required checks, capture fresh outputs from tests and builds, and attach them to justify your completion claim.

What is evidence-based completion in continuous integration?▼

Evidence-based completion in continuous integration is the practice of requiring fresh verification outputs from builds and tests before any success statement is reported, ensuring claims are always backed by proof.

How do I enforce QA checkpoints before declaring a task complete?▼

You enforce QA checkpoints by running verification steps like tests, lint, and builds, capturing their fresh outputs, and only reporting a completion decision when the evidence shows all checks pass.

Does this verification approach work without external dependencies?▼

Yes, this verification approach works without external dependencies. It functions independently to guide teams on where and how to verify work and report results within your existing software development workflows.

When should I not use automated verification before completion?▼

You should not use automated verification before completion for tasks outside software development workflows, pull requests, testing, builds, and QA checkpoints, as its logic specifically targets evidence-based completion in these contexts.