gtkb-decision-capture

Insert append-only Deliberation Archive records with collision-safe DELIB-ID handling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents important yes/no and tradeoff choices from being lost after a session by capturing them as durable, governed Deliberation Archive records that can be reused later for continuity and accountability.

Core Features & Use Cases

  • Captures owner decisions as append-only Deliberation Archive entries (fixed governance metadata for consistent discovery).
  • Enforces DELIB-ID collision safety so repeated IDs fail explicitly rather than silently creating unrelated history.
  • Supports traceability links by optionally attaching related spec/work-item references and session/participant context.

Use case example: An owner approves a rejected-alternative design choice (e.g., selecting one architecture over another); record the decision so future Prime Builder/Loyal Opposition rounds inherit the original rationale.

Quick Start

Capture an owner’s scope or design decision by providing a fresh DELIB-ID, a title and summary, and the decision content to be stored in the Deliberation Archive.

Frequently Asked Questions about gtkb-decision-capture

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

FAQPage Schema
How do I capture architectural decisions and tradeoffs for future traceability?

Capturing architectural decisions involves recording them as append-only Deliberation Archive entries with fixed governance metadata. This preserves durable rationale and traceability across sessions by storing the decision content, source type, and outcome.

What is a Deliberation Archive record for decision capture?

A Deliberation Archive record is an append-only entry that stores an owner's yes/no or tradeoff decision. It includes a unique DELIB-ID, title, summary, and optional links to related spec or work-item references for consistent future discovery.

How do I record rejected design alternatives during project development?

To record rejected design alternatives, provide a fresh DELIB-ID, a title, summary, and the decision content. The system inserts this as a Deliberation Archive entry, ensuring future workflows inherit the original rationale behind the design selection.

Does decision capture enforce unique IDs to prevent history collisions?

Yes, decision capture enforces DELIB-ID collision safety. If a repeated ID is detected, the system raises an explicit error rather than silently creating unrelated history, ensuring the integrity of your governance knowledge base.

Can I attach session and participant context to an architecture decision record?

Yes, you can optionally attach related spec or work-item references along with session and participant context. This metadata is stored alongside the decision content in the Deliberation Archive to support traceability links.

What happens if there is an unexpected failure during decision capture?

If an unexpected insert failure occurs, the system raises explicit errors rather than failing silently. This ensures that only successfully persisted rows are returned, maintaining the strict append-only integrity of the Deliberation Archive.