gtkb-bridge-propose

Creates credential-safe bridge proposals with mandatory specification links and atomic index updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you draft and persist implementation bridge proposals that are safe to store and reviewable by enforcing credential-scan redaction, mandatory specification linkage, and concurrency-safe updates to the bridge index.

Core Features & Use Cases

  • Credential-safe proposal persistence: scans proposal bodies against credential catalogs and either aborts or redacts credential-shaped spans before any file is written.
  • Mandatory specification linkage gate: requires a Specification Links section with concrete spec IDs or governing rule file paths and rejects placeholder-only submissions.
  • Governance-ready bridge artifacts: writes the proposal to bridge/<topic>-001.md and inserts a Document + NEW entry into bridge/INDEX.md with atomic, retry-safe concurrency handling.
  • Prior deliberations pre-population: optionally pre-populates the proposal’s Prior Deliberations section using glossary seeding plus best-effort semantic retrieval for faster review and pruning.

Quick Start

Use gtkb-bridge-propose to create a new bridge proposal for a topic by providing the topic slug and proposal body with a filled Specification Links section so the helper can write bridge/<topic>-001.md and update bridge/INDEX.md.

Frequently Asked Questions about gtkb-bridge-propose

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

FAQPage Schema
How do I create governance-safe bridge proposals with mandatory specification links?

To create governance-safe bridge proposals, you provide a topic slug and proposal body containing concrete specification links. The system validates these mandatory spec links, rejects placeholder-only submissions, and writes a versioned bridge document while atomically updating the bridge index.

How are bridge proposals persisted and indexed safely during concurrent updates?

Bridge proposals are persisted by writing to bridge/<topic>-001.md and inserting a Document + NEW entry into bridge/INDEX.md. This process uses concurrency-safe insertion logic with retry limits to ensure atomic updates.

Do I need to manually populate prior deliberations when creating a bridge proposal?

No, manual population is not required. The system optionally pre-populates the Prior Deliberations section using glossary seeding plus best-effort semantic retrieval from canonical sources, accelerating review and pruning.

What happens if I only provide placeholder specification links in my bridge proposal?

If you only provide placeholder specification links, the submission is rejected. A mandatory specification linkage gate requires concrete spec IDs or governing rule file paths to pass validation.