blueprint:supersede

Replace or deprecate ADRs while preserving decision history and rationale.

2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/rickardp/blueprint-mode --skill blueprint-supersede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint:supersede
Source: https://github.com/rickardp/blueprint-mode/tree/main/plugins/blueprint-mode/skills/supersede
Command: npx skills add https://github.com/rickardp/blueprint-mode --skill blueprint-supersede

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replacing or deprecating architectural decisions while preserving historical context and rationale.

Core Features & Use Cases

  • Provides a formal process to replace a decision with a new one, or deprecate it when no replacement exists.
  • Preserves history through updated frontmatter and linked references, while guiding the user through required notes and migration steps.
  • Use cases include updating technology choices, retiring outdated ADRs, and documenting rationale for governance.

Quick Start

Initiate a supersede action by requesting a replacement ADR with the new decision and context.

Frequently Asked Questions about blueprint:supersede

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

FAQPage Schema
How do I supersede an ADR while maintaining decision history?

To supersede an ADR while maintaining decision history, you must identify the outdated ADR, provide the replacement decision, document the rationale, and add any migration notes to ensure an auditable record.

What is the process to deprecate an architectural decision when no replacement exists?

Deprecating an architectural decision without a replacement requires documenting the rationale for retirement and updating the ADR frontmatter to preserve historical context and traceability across projects.

When do I need to replace an ADR instead of simply updating it?

You need to replace an ADR instead of updating it when a fundamental technology choice changes, requiring a formal replacement decision, migration notes, and an auditable versioned record to preserve history.

What information is required to supersede a prior architectural decision?

Superseding a prior architectural decision requires the identification of the ADR to supersede, the new replacement decision, the rationale for the change, and any necessary migration notes.

Does superseding an ADR preserve the original decision rationale for governance?

Superseding an ADR preserves the original rationale for governance by maintaining a coherent decision history through updated frontmatter, linked references, and required migration notes.