gtkb-bridge

Coordinate versioned bridge thread proposals, reviews, and verifications via INDEX.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination problem of managing implementation proposals, reviews, and verification as versioned bridge artifacts with strict lifecycle states and mandatory validation gates.

Core Features & Use Cases

  • Bridge lifecycle operations: Propose (NEW/REVISED), scan queue state, revise drafts after NO-GO, respond with GO/NO-GO/VERIFIED verdicts, verify via post-implementation reports, and check thread status without mutation.
  • INDEX-driven queue discipline: Uses bridge/INDEX.md as the canonical source of queue state and lifecycle ordering, ensuring both roles operate on the correct latest entries.
  • Governance safety gates: Enforces required applicability and clause preflights, specification linkage requirements, credential-scan handling, and owner-decision section enforcement for owner-approval-dependent work.
  • Deterministic helper-backed actions: Delegates file-writing and thread inspection to helper scripts that standardize parsing, sorting, drift detection, and formatting.

Quick Start

Use the skill to propose a bridge thread for a topic slug that requires Loyal Opposition review and then follow the lifecycle states until verification is completed.

Frequently Asked Questions about gtkb-bridge

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

FAQPage Schema
How do I coordinate AI-assisted software development proposals and reviews using a bridge protocol?

A bridge protocol coordinates file-based implementation proposals and reviews by applying strict lifecycle states, mandatory validation gates, and INDEX-driven queue discipline to manage versioned markdown threads. This ensures deterministic GO or NO-GO verdicts for development tasks.

What is a go no-go verdict in implementation verification?

A go no-go verdict is a governance gate decision applied to implementation proposals. It requires reading the full version chain and enforcing specification linkage to determine whether a proposed software change proceeds to implementation or requires revision.

How do I enforce governance gates for spec-to-test mapping in versioned markdown threads?

You enforce governance gates by running mandatory preflights on applicability and clauses, verifying specification linkage requirements, and executing credential-scan-safe writes. This ensures spec-to-test mapping integrity before applying lifecycle state machine transitions.

Can I scan the bridge queue state without mutating lifecycle state machine entries?

Yes, you can check thread status without mutation by scanning the bridge INDEX file. This canonical source provides the latest queue state and lifecycle ordering, allowing safe inspection of versioned implementation threads before applying any verdicts.

Why does implementation verification require full version-chain reading for verdict correctness?

Full version-chain reading is required because versioned markdown threads accumulate revisions after NO-GO decisions. Reading the entire chain ensures deterministic helper-backed parsing and drift detection, preventing incorrect VERIFIED verdicts on outdated proposal states.