verification-before-completion

Verify tests, builds, and requirements before declaring task completion.

2|Updated Apr 13, 2026

Search Tags:#quality assurance #code review #verification #test-driven development #task completion

Ready to run

npx skills add https://github.com/VidyaBodepudi/Code-Skills --skill verification-before-completion-vidyabodepudi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/VidyaBodepudi/Code-Skills/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/VidyaBodepudi/Code-Skills --skill verification-before-completion-vidyabodepudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that work is actually done before declaring completion, preventing the anti-pattern of declaring success without evidence.

Core Features & Use Cases

Verification Checklist: Confirms all tests pass, build succeeds, requirements are met, and no regressions are introduced.
Evidence Requirement: Provides evidence for each completed task, including test output, build output, and requirement mapping.
Prevents Misleading Completion: Stops the declaration of completion until all criteria are met, ensuring high-quality deliverables.

Quick Start

Run the verification checklist before declaring any task complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify all tests pass and the build succeeds before declaring task completion?▼

To verify task completion, run an automated checklist that confirms all tests pass, the build succeeds, requirements are met, and no regressions are introduced before declaring success.

What is task verification in test-driven development?▼

Task verification in test-driven development is the process of requiring concrete evidence, such as test output and build logs, to prove a task is fully complete without introducing regressions.

How do I stop misleading completion declarations in my software development workflow?▼

Stop misleading completion declarations by enforcing an evidence requirement that blocks task completion until build output, test results, and requirement mapping are successfully verified.

Can I use a verification checklist to map requirements before completing a code review?▼

Yes, you can use a verification checklist during a code review to map requirements, confirm all tests pass, and ensure the build succeeds before allowing task completion.

What's the best way to ensure quality assurance standards are met before a task is done?▼

The best way to ensure quality assurance standards is to mandate a verification checklist that provides concrete test output and build evidence before any task is marked complete.

Why should I require evidence for completed software development tasks?▼

You should require evidence for completed tasks to prevent the anti-pattern of declaring success without proof, ensuring high-quality deliverables by verifying tests, builds, and requirements.