gtkb-verify

Generates a post-implementation VERIFIED or NO-GO verdict file for Loyal Opposition review.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill gtkb-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtkb-verify
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill gtkb-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how Loyal Opposition authors record a post-implementation VERIFED or NO-GO verdict that passes the Mandatory Specification-Derived Verification Gate, preventing missing evidence and inconsistent bridge artifacts.

Core Features & Use Cases

  • Verdict file scaffolding: Generates the structural conventions for a verification verdict file, including applicability and clause preflight sections, evidence citations, and required sections for both VERIFIED and NO-GO.
  • Spec-to-test coverage enforcement support: Ensures the verdict includes the mandatory spec-to-test mapping table with executed results as the basis for gate enforcement decisions.
  • Bridge workflow alignment: Directs the author to reference the full thread history and prior deliberations, while keeping bridge/INDEX.md updates out of scope.

Quick Start

Ask the assistant to write a verification verdict for the specified bridge thread by running /verify <slug> and having you paste the required preflight outputs and test results into the scaffolded verdict file.

Frequently Asked Questions about gtkb-verify

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

FAQPage Schema
How do I generate a verification verdict for a post-implementation bridge thread?▼

To generate a verification verdict, run the verify command with your bridge slug and paste the required preflight outputs and test results into the scaffolded verdict file. This produces a spec-backed VERIFIED or NO-GO verdict for Loyal Opposition review.

What is spec-derived testing and when is a verification verdict required?▼

Spec-derived testing maps specification clauses to executed test results within a verdict file. A verification verdict is required when a bridge thread needs formal verification of an implementation report after a GO decision has occurred.

How do I format a NO-GO verdict with missing evidence documentation?▼

A NO-GO verdict requires correct verdict formatting and specific gate-honoring sections for NO-GO evidence and owner action. You must include the verbatim preflight outputs, executed spec-to-test rows, and structural documentation of applicability findings.

Does the verification verdict process update the bridge workflow index?▼

No, the verification verdict process explicitly keeps bridge/INDEX.md updates out of scope. It directs the author to reference the full thread history and prior deliberations while focusing solely on producing the specification-derived verification gate artifact.

What sections are mandatory in a specification-derived verification gate file?▼

Mandatory sections in a verification gate file include structural documentation of applicability, clause preflight, deliberation citations, spec-to-test coverage mapping with executed results, findings, and required commands for both VERIFIED and NO-GO outcomes.

Can I use this verification process without prior deliberation citations in the bridge thread?▼

No, the verification verdict requires inclusion of deliberation citations from the full thread history. The scaffold directs the author to reference prior deliberations to satisfy the Loyal Opposition review requirements.