Create architecture decision records with ADR-* IDs in the Knowledge Database.
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-adr
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
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.
type='architecture_decision' and ADR-* IDs so they are discoverable and governed.Ask the AI to create an ADR for your next architecture choice: /kb-adr "Use Postgres instead of MongoDB for the primary datastore".
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Community-ChestsClassify governance decisions with required tags and two-person review.
ekremmkasapDocument architecture decisions with standardized ADR templates and lifecycle tracking.
abudhahirGenerate system architecture documentation and Architecture Decision Records.
Euraika-LabsCreate Architecture Decision Records with required sections for game development projects.