skills.rest
Refinex-Space
Refinex-SpaceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-verify

Require fresh verification evidence before completion claims in Harness workflows.

Updated Aug 23, 2026
Search Tags:#validation#verification#handoff#verify#claims#tests#harness
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-verify
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/plugins/harness-powers/skills/harness-verify
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

False completion claims threaten project integrity; harness-verify prevents them by requiring fresh verification evidence before any success claim.

Core Features & Use Cases

  • Enforces a fresh-evidence gate before any completion claim across feature work, bug fixes, drift repairs, and control-plane updates.
  • Provides a clear announce-at-start protocol to set expectations and record verification steps.
  • Supports integration with Harness workflows to validate acceptance criteria, tests, and validation results prior to handoff.

Quick Start

Announce at the start and provide fresh verification evidence before declaring completion or handing off work.

Frequently Asked Questions about harness-verify

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

FAQPage Schema
How do I prevent false completion claims during software handoff?▼

Prevent false completion claims by enforcing a fresh verification evidence gate that mandates explicit tests and validation steps prior to any handoff or release.

What is verification evidence freshness and when do I need it for feature work?▼

Verification evidence freshness requires recent test and validation results before declaring success. You need it for feature work, bug fixes, drift repairs, and control plane updates.

How to enforce validation steps before releasing bug fixes or control plane updates?▼

Enforce validation steps by applying an announce-at-start protocol across Harness workflows, requiring explicit tests and fresh validation results before approving any release.

Does harness-verify work with Harness workflows for drift repairs and feature work?▼

Yes, harness-verify integrates with Harness workflows to validate acceptance criteria, tests, and validation results prior to handoff across feature work and drift repairs.

What is the best way to mandate tests before declaring a bug fix complete?▼

The best way to mandate tests before completion is applying a verification discipline gate that blocks success claims until fresh test evidence is explicitly provided and recorded.

Why does requiring fresh verification evidence matter for control plane updates?▼

Requiring fresh verification evidence matters because it prevents false completion claims and ensures project integrity by validating explicit tests prior to any control plane update release.

Related Skills

Explore More Software Engineering Skills→
alo-expalo-exp
6

gsd-verify-work

Execute PLAN.md verification steps and generate VERIFICATION.md with results.

Official
Intermediate
Fandry96Fandry96
27

verification-before-completion

Run fresh verification commands and report evidence before declaring completion.

Community
Advanced
homeassistant-aihomeassistant-ai
4.3k

bat-adhoc

Run BAT tests via tests/uat/run_uat.py to validate MCP tools from an AI agent's perspective.

Official
Intermediate
jscraikjscraik
8

verification-before-completion

Verify completion claims with fresh command output before merging.

Community
Advanced