team-verification-before-completion

Name: team-verification-before-completion
Availability: InStock
Author: davekim917

Enforce a five-step verification gate before declaring tasks complete.

1|Updated Mar 6, 2026

Search Tags:#workflow #verification #audit #completion #quality #claims

Ready to run

npx skills add https://github.com/davekim917/bootstrap --skill team-verification-before-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-verification-before-completion
Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-verification-before-completion
Command: npx skills add https://github.com/davekim917/bootstrap --skill team-verification-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-cutting verification guard that enforces evidence-based completion by requiring fresh verification output before any task can be declared done. Applies across all workflow stages: /team-build, /team-qa, /team-ship, /team-debug, /team-tdd, and direct implementation. It covers software tests, ML metrics, pipeline runs, query results, dashboard rendering, and schema validation. Use when an agent claims work is done or signals task completion. Do not use for intermediate progress updates or partial status reports.

Core Features & Use Cases

Enforces a formal completion gate that requires explicit verification evidence before marking work complete.
Applies across software development, data pipelines, ML evaluation, dashboards, and analytics for consistent quality control.
Provides a concrete five-step workflow (IDENTIFY, RUN, READ, VERIFY, CLAIM) to prevent premature completion claims.

Quick Start

Before reporting task completion, trigger the verification gate and execute IDENTIFY → RUN → READ → VERIFY → CLAIM with attached evidence.

Frequently Asked Questions about team-verification-before-completion

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

FAQPage Schema

How do I enforce evidence-based task completion before declaring work done?▼

Evidence-based task completion requires fresh verification output before marking work complete. You enforce this by applying a five-step gate (IDENTIFY, RUN, READ, VERIFY, CLAIM) that blocks premature completion claims until verification output passes.

What is the best way to prevent premature completion claims in software workflows?▼

Preventing premature completion claims involves triggering a formal verification gate across workflow stages like team-build, team-qa, and team-ship. This ensures explicit verification evidence is attached before any task completion status is accepted.

Can I use verification gates for ML metrics and data pipelines?▼

Yes, verification gates apply across ML metrics, data pipelines, query results, dashboard rendering, and schema validation. They require fresh verification output across these domains before declaring tasks done.

How do I implement a completion gate step by step?▼

Implement a completion gate by executing the IDENTIFY, RUN, READ, VERIFY, CLAIM workflow. Before reporting task completion, trigger the gate and attach the evidence generated from the fresh verification output.

When should I not use task verification gates?▼

Task verification gates should not be used for intermediate progress updates or partial status reports. They are designed exclusively for moments when an agent claims work is done or signals task completion.

Does evidence-based verification work with team-tdd and team-debug workflows?▼

Evidence-based verification works with team-tdd, team-debug, team-build, team-qa, and team-ship workflows. It provides consistent quality control across all these software development stages by requiring fresh verification output.