kb-adr

Create architecture decision records with ADR-* IDs in the Knowledge Database.

2|1|Updated Mar 30, 2026

Search Tags:#software architecture #governance #ADR #rationale #architecture decision record #knowledge database

Ready to run

npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-adr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kb-adr
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-adr
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents architecture decisions from being lost or re-litigated by creating durable, searchable ADR records in the Knowledge Database, including rationale, consequences, and rejected alternatives.

Core Features & Use Cases

Creates ADR specifications in the Knowledge Database: Stores decisions as specs with type='architecture_decision' and ADR-* IDs so they are discoverable and governed.
Guides complete decision documentation: Prompts for context, decision, failed approaches, consequences, and alternatives rejected to preserve “why” over time.
Supports listing existing ADRs: Reads existing ADRs from the KB and prints their IDs, statuses, and titles for quick review.

Quick Start

Ask the AI to create an ADR for your next architecture choice: /kb-adr "Use Postgres instead of MongoDB for the primary datastore".

Frequently Asked Questions about kb-adr

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

FAQPage Schema

How do I document architecture decisions so the rationale is preserved for future teams?▼

Create architecture decision records in a knowledge database to capture context, rationale, consequences, and rejected approaches for governance-driven changes. This ensures the "why" behind decisions is traceable and durable over time.

What is the best way to prevent architecture decisions from being re-litigated by the team?▼

Store architecture decisions as searchable ADR records with allocated IDs in a knowledge database. Capturing failed approaches and alternatives rejected prevents teams from repeatedly debating the same architectural choices.

How do I generate an architecture decision record and allocate the correct ID?▼

Use an ADR generation process that automatically allocates the next sequential ADR-* ID and inserts the specification into the knowledge database with the correct type and tags for discovery.

Can I list existing architecture decision records to review their current statuses?▼

Yes, reading existing ADRs from the knowledge database prints their IDs, statuses, and titles for quick review. This allows teams to survey past architecture decisions before making new governance-driven changes.

What context should an architecture decision record include for governance-driven changes?▼

An architecture decision record should include the context, the decision itself, failed approaches, consequences, and alternatives rejected. This complete documentation preserves the reasoning needed before implementation and future revisits.

When do I need to create an ADR instead of just writing standard documentation?▼

Create an ADR when governance-driven architecture changes require traceable rationale before implementation begins. It is specifically necessary when teams need to preserve the "why" behind a decision for future revisit and compliance.