supersede

Supersede Architecture Decision Records with dependency graphs and user approval.

4|1|Updated Apr 25, 2026

Search Tags:#ADR #architecture decisions #code governance #supersession #decision record management

Ready to run

npx skills add https://github.com/rvdbreemen/adr-kit --skill supersede-rvdbreemen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supersede
Source: https://github.com/rvdbreemen/adr-kit/tree/main/skills/supersede
Command: npx skills add https://github.com/rvdbreemen/adr-kit --skill supersede-rvdbreemen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of superseding an existing Architecture Decision Record (ADR) with a new one, ensuring a clear and controlled transition without rewriting history.

Core Features & Use Cases

ADR Supersession: Guided through the process of creating a new ADR that supersedes an old one, maintaining the integrity of the decision-making chain.
Dependency Graph Display: Shows the dependency graph of the target ADR to help identify related decisions that may need updating.
User Approval Workflow: Ensures explicit user approval before making changes to the old ADR, minimizing the risk of mistakes.

Quick Start

Run /adr-kit:supersede ADR-OLD to supersede an existing ADR with a new decision.

Frequently Asked Questions about supersede

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

FAQPage Schema

How do I supersede an Architecture Decision Record without losing the decision chain?▼

Superseding an Architecture Decision Record involves creating a new ADR that explicitly replaces the old one while preserving the original document for historical integrity. The process verifies the decision chain and displays dependency graphs to identify related decisions requiring updates.

When do I need to supersede an ADR instead of editing it directly?▼

You need to supersede an ADR instead of editing it directly when a previous architecture decision is no longer valid and must be replaced by a new decision. Supersession maintains a controlled transition and preserves the decision-making history without rewriting past records.

Does ADR supersession require explicit user approval before modifying old records?▼

Yes, ADR supersession requires explicit user approval before making any changes to the old ADR. This user approval workflow minimizes the risk of mistakes and ensures a controlled replacement of old decisions with new ones.

How do I identify related architecture decisions that need updating when superseding an ADR?▼

You can identify related architecture decisions by reviewing the dependency graph displayed during the supersession process. This graph shows the dependencies of the target ADR, helping you see which other decisions may need updating based on the new changes.

What's the best way to manage code governance for architecture decisions?▼

Managing code governance for architecture decisions is best handled by using ADR supersession to control how old decisions are replaced. This approach ensures decision record integrity through dependency checks, explicit approvals, and maintaining a clear chain of supersession.

Can I supersede multiple ADRs at the same time?▼

The metadata does not specify whether multiple ADRs can be superseded simultaneously. The standard workflow guides you through superseding a single target ADR, verifying its decision chain and dependencies before proceeding with the replacement.