qa-gate-disciplined-completion

Verify QA gate artifacts, tests, and lint before marking tasks complete.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill qa-gate-disciplined-completion-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-gate-disciplined-completion
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/generated/qa-gate-disciplined-completion
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill qa-gate-disciplined-completion-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often mark tasks or phases complete without running tests, checking lint, or producing required evidence artifacts, causing revert-triggering gaps and plan/reality divergence. This Skill enforces a disciplined verification checklist before any completion claim. ## Core Features & Use Cases - Artifact Verification: Confirms required QA gate evidence files exist in .swarm/evidence/ before completion is claimed. - Test and Lint Enforcement: Requires actually running the test suite and ruff check on changed files, verifying zero errors in real output. - Phase Completion Guard: Blocks phase_complete calls while any task remains in_progress and requires explicit success criteria (lint, typecheck, coverage, test count). - Use Case: Before closing a development phase, an agent runs the full checklist—artifacts present, tests passing, lint clean on the diff, no in-progress tasks—then safely calls phase_complete. ## Quick Start Before marking this task complete, verify all QA gate artifacts exist, run the test suite and ruff on changed files, and confirm no tasks are still in progress.

Frequently Asked Questions about qa-gate-disciplined-completion

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

FAQPage Schema
How do I verify a task is complete before marking it done?▼

Run the full verification checklist: confirm required QA gate artifacts exist in .swarm/evidence/, run the test suite and verify passes in actual output, run ruff check on changed files with zero errors, and confirm all agreed success criteria are met.

What QA gate artifacts are required before claiming completion?▼

Required evidence files such as drift-verifier.json and hallucination-guard outputs must exist and be populated in the .swarm/evidence/ directory. Claiming completion without this evidence is a revert-triggering gap.

When is it safe to call phase_complete?▼

Only call phase_complete after checking that no task in the phase still has in_progress status. Calling it early creates plan/reality divergence that blocks future planning operations.

Should lint verification cover the whole repo or only changed files?▼

Scope lint and typecheck verification to the diff of changed files, or ensure the baseline has no pre-existing CI failures. Pre-existing failures must be fixed or explicitly suppressed before phase-end verification.

Why did my completion claim get reverted?▼

Reverts typically happen when required evidence artifacts are missing, tests were not actually run, or lint failures exist on touched files. Checking a box without running verification counts as a skipped gate.