verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: facostarr

Enforces evidence-based verification workflows before software tasks are considered complete.

Updated Oct 29, 2025

Search Tags:#best practices #development workflow #verification #software quality #evidence-based

Ready to run

npx skills add https://github.com/Facostarr/lagencesauvage.com2 --skill verification-before-completion-facostarr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Facostarr/lagencesauvage.com2/tree/main/docs/skills/verification-before-completion
Command: npx skills add https://github.com/Facostarr/lagencesauvage.com2 --skill verification-before-completion-facostarr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill promotes a culture of thoroughness and honesty by enforcing the verification of work before making completion claims.

Core Features & Use Cases

Verification Workflow: Standardizes the process of verifying work before claiming completion.
Evidence-Based Claims: Encourages evidence of verification before making assertions about work status.
Use Case: Before merging code into a repository, run verification commands and confirm results using this Skill's framework.

Quick Start

Use the verification-before-completion skill to ensure your work is complete by running all verification commands and reviewing the output.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I enforce evidence-based verification before claiming software development is complete?▼

Evidence-based verification requires running testing, linting, and building commands to produce concrete output before making any work completion claims. This framework standardizes the process of checking software quality through external tools.

What is the best way to verify code quality before merging into a repository?▼

The best way to verify code quality before merging is to execute all verification commands manually and review the output. This framework requires evidence of successful testing, linting, and building before asserting work completion.

Do I need external tools to verify work completion in a development workflow?▼

Yes, verifying work completion requires external tools for testing, linting, and building. The framework mandates manual execution of these tools to gather evidence before making any success claims about your software.

How to standardize the verification workflow for software quality assurance?▼

Standardizing software quality verification involves enforcing a workflow that requires running all testing and linting commands first. You must review the external tool output as evidence before making any assertions about development completion.

Why does my development workflow lack evidence before completion claims?▼

Development workflows lack evidence when they skip verifying work through testing, linting, and building. This framework solves that by enforcing a culture of thoroughness requiring external tool output as proof before claiming success.

When should I not use an evidence-based verification framework?▼

You should not use an evidence-based verification framework if you cannot manually execute external testing and building tools. The framework strictly requires running verification commands and reviewing their output before making completion assertions.