skills.rest
Brite-Nites
Brite-NitesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforce multi-level build, test, acceptance, and integration verification before task completion.

Updated Jan 14, 2026
Search Tags:#testing#verification#linear#ci-cd#quality-assurance#acceptance-criteria#task-completion
One-click install
npx skills add https://github.com/Brite-Nites/brite-claude-plugins --skill verification-before-completion-brite-nites
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Brite-Nites/brite-claude-plugins/tree/main/plugins/workflows/skills/verification-before-completion
Command: npx skills add https://github.com/Brite-Nites/brite-claude-plugins --skill verification-before-completion-brite-nites

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures tasks are genuinely resolved before marking them done by validating fixes, tests, and acceptance criteria at every checkpoint in the plan execution.

Core Features & Use Cases

  • Multi-level verification protocol: Level 1 Build Verification, Level 2 Test Verification, Level 3 Acceptance Criteria, Level 4 Integration Verification.
  • Checkpoint-driven validation: Activates at plan checkpoints and before shipping to prevent premature closure.
  • Failure handling & reporting: Clear failure reports with next steps and retry limits.
  • Completion integrity & traceability: Ensures changes are production-ready with issue-to-task traceability.

Quick Start

Enable verification in your plan workflow and run the built-in checks at each checkpoint to ensure fixes pass, tests succeed, and acceptance criteria are met before closing a task.

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 task completion in CI/CD development workflows?▼

Prevent premature task completion by enforcing a multi-level verification protocol at plan execution checkpoints, validating that fixes work, tests pass, and acceptance criteria are met before closing issues.

What is multi-level verification for bug fixes and task closure?▼

Multi-level verification is a protocol validating build, test, acceptance criteria, and integration success before closing Linear issues, ensuring changes are production-ready and traceable.

How to verify acceptance criteria are met before closing Linear issues?▼

Verify acceptance criteria by activating checkpoint-driven validation prior to closing Linear issues, running built-in checks that validate fixes pass and tests succeed before marking a task done.

What happens when a verification check fails before shipping?▼

When verification fails before shipping, the protocol generates clear failure reports with next steps and retry limits to guide remediation and prevent premature closure.

Does this verification protocol work without external dependencies?▼

Yes, the verification protocol operates without external dependencies, applying checkpoint-driven validation directly within your development workflows to ensure completion integrity.

Related Skills

Explore More Product & Management Skills→
usuroborusurobor
8

issue/proof

Define acceptance criteria and proof plans for cnos issues with invariants, oracles, and surfaces.

Community
Advanced
oborchersoborchers
28

tag-based-production-deploys

Enforce git tag-based production deployments with manual approval gates.

Community
Advanced
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
MelvynxMelvynx
223

apex

Orchestrate adaptive agents to plan, execute, and validate feature implementations.

Community
Advanced