adr-supersede

Supersede an accepted Architecture Decision Record by pairing it with a successor via the adr MCP tool.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill adr-supersede-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-supersede
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/adr-supersede
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill adr-supersede-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rolling back an accepted Architecture Decision Record without corrupting project history is error-prone: hand-editing statuses or deleting records breaks the decision graph. This Skill retires a decision the correct way by atomically pairing the old record with a successor, flipping only the old record's header status to superseded while leaving its content byte-identical. ## Core Features & Use Cases - Two-sided supersession: The adr MCP tool's supersede action links both records — the old one points to its successor, the successor carries the Supersedes link back — in one validated operation. - Two successor modes: Create a new proposed skeleton record from a title, or pair an already-drafted existing record as the replacement. - Fail-closed refusals: Clear refusal table covering already-superseded records, self-supersession, unparseable headers, slug failures, and numbering conflicts, with a path forward for each. - Use Case: Your team decided on REST in ADR-0007 but is moving to gRPC. Run this Skill to mark ADR-0007 as superseded, generate a linked draft for the gRPC decision, then fill it in and route it through the normal review and accept gates. ## Quick Start Ask the assistant to supersede ADR-0007 with a new decision titled "Adopt gRPC for inter-service communication" using the adr supersede workflow.

Frequently Asked Questions about adr-supersede

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

FAQPage Schema
How do I supersede an Architecture Decision Record?▼

Call the adr MCP tool with the supersede action, passing the old record's number plus either a title for a new replacement or the number of an existing successor record. The tool flips the old record's status to superseded and links both records in both directions.

Should I edit or delete an old ADR when a decision changes?▼

No. A superseded record's content stays byte-identical; only its header status changes to superseded with a link to the successor. Deleting or hand-editing breaks the decision graph and creates the one-way link corruption that ADR audits exist to catch.

Can I supersede a proposed ADR draft that is simply wrong?▼

No. Supersession is reserved for decisions that carried authority, meaning accepted records or deprecated ones being formally replaced. A wrong proposed draft should just be edited or removed directly.

Why does the adr supersede action refuse my request?▼

Refusals are fail-closed and specific: the record may already be superseded, both or neither replacement modes given, the successor may equal the old number, the title may yield no usable slug, or a header may be unparseable. Each refusal names the fix; never bypass by hand-editing.

What happens to the new successor record after supersession?▼

A newly created successor starts as a proposed skeleton with placeholder sections and the Supersedes link already in place. You fill in context, decision, and consequences, then run it through the normal ADR review and accept gates like any draft.