Does this skill delete my old documentation files?

By default, it updates the status to 'Superseded' or 'Deprecated'. It only suggests deleting the file if no code references remain, as Git history serves as the permanent archive.

Can I provide migration notes during a replacement?

Yes, the replacement flow specifically prompts for migration notes and the reasoning behind the change to populate the new ADR template.

What happens if I make a mistake while superseding?

The skill includes error recovery steps that allow you to revert frontmatter status changes or update the intent if the wrong action was taken.

How does Claude identify which ADR to change?

The skill uses globbing to search your `docs/adrs/` directory and can identify the correct record via ADR number or title.

ADR Lifecycle & Supersede

Name: ADR Lifecycle & Supersede
Author: rickardp

byrickardp

•

Aprendizaje y Documentación

Manages the evolution of architectural decisions by replacing outdated specs or deprecating retired functionality.

This skill automates the complex task of maintaining Architectural Decision Records (ADRs) as a project evolves. It provides a structured workflow for developers to either replace an existing decision with a new one or retire functionality entirely. By handling frontmatter updates, generating new documentation from templates, and scanning the codebase for stale references, it ensures your project's architectural source of truth remains synchronized with your actual implementation while preserving historical context through Git.

Características Principales

01Interactive intent detection for architectural changes

02Standardized documentation template generation

03Codebase scanning for stale ADR references

041 GitHub stars

05Automated ADR replacement and deprecation workflows

06Automatic frontmatter status and metadata management

Casos de Uso

01Updating technical decisions to reflect new project constraints or technology shifts

02Deprecating a legacy caching strategy and identifying related code for removal

03Replacing a REST-based architecture with GraphQL and updating all related documentation

Características Principales

01Interactive intent detection for architectural changes

02Standardized documentation template generation

03Codebase scanning for stale ADR references

041 GitHub stars

05Automated ADR replacement and deprecation workflows

06Automatic frontmatter status and metadata management

Casos de Uso

01Updating technical decisions to reflect new project constraints or technology shifts

02Deprecating a legacy caching strategy and identifying related code for removal

03Replacing a REST-based architecture with GraphQL and updating all related documentation