pm-verification-protocols

Enforce QA verification gates with evidence before task completion.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-verification-protocols-bobmatnyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-verification-protocols
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-verification-protocols
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-verification-protocols-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This protocol enforces dedicated QA verification before closing tasks, ensuring evidence is collected and reviewed.

## Core Features & Use Cases

  • Enforce mandatory QA delegation and evidence collection
  • Define required evidence per work type
  • Circuit-breaker enforcement to prevent premature completion

### Quick Start Delegate a task to QA and attach verification evidence before marking it complete.

Frequently Asked Questions about pm-verification-protocols

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

FAQPage Schema
How do I enforce QA verification gates before a task can be marked complete?

QA verification gates require delegated QA review and attached evidence before allowing status changes. This protocol blocks premature task completion by enforcing evidence collection across UI, API, and database workflows.

What is a circuit-breaker action in QA governance?

A circuit-breaker action in QA governance triggers when non-compliance is detected, halting task progress automatically. It stops status changes by enforcing QA-automation checks and intercepting forbidden phrases until evidence is provided.

How do I require specific evidence for different types of QA verification?

Specifying required evidence per work type allows you to define exact verification artifacts needed for UI, API, database, local, and deployed tasks. This ensures QA delegation matches the evidence requirements before status changes occur.

Can I use automated QA checks to gate progress and prevent premature task completion?

Yes, QA-automation checks can gate progress by blocking status changes until compliance is met. The protocol specifies automated checks that intercept forbidden phrases and enforce evidence attachment before task completion is allowed.

Does QA verification governance work for both local and deployed environments?

QA verification governance works across local and deployed environments, applying consistent evidence gates to UI, API, and database workflows. This ensures verification protocols enforce compliance regardless of where the work occurs.

Why does my workflow allow task completion without QA evidence?

Task completion without QA evidence occurs when workflows lack enforced verification gates and circuit-breaker actions. Implementing this protocol blocks status changes by mandating evidence attachment and intercepting forbidden phrases.