How does the superseding workflow work?

The skill provides scripts to mark an old ADR as 'superseded' and automatically create a new one, maintaining a linked history of how your technical decisions have evolved over time.

An Architecture Decision Record (ADR) is a short text file that captures a significant architectural decision, including the context in which it was made and the consequences it has for the project.

Can I search through my project's decision history?

Absolutely. The skill includes search capabilities that scan titles, contexts, and consequences, allowing you to quickly find why a specific decision was made in the past.

Does this skill follow a specific documentation standard?

Yes, it follows the industry-standard Michael Nygard ADR format, which ensures all decisions include title, status, context, decision, and consequences.

Architecture Decision Tracking

Name: Architecture Decision Tracking
Author: vanman2024

byvanman2024

•

Learning & Documentation

Manages Architecture Decision Records (ADRs) with automated templates, sequential numbering, and lifecycle tracking to document technical choices.

About

This skill provides a comprehensive framework for managing Architecture Decision Records (ADR) based on the Michael Nygard format. It streamlines the process of documenting significant technical decisions by providing automated scripts for creation, sequential numbering, status management, and indexing. It is particularly useful for engineering teams who need to maintain a 'living history' of architectural choices, ensure transparency across stakeholders, and handle the evolution of a codebase through formal superseding workflows and decision matrices.

Key Features

Automated ADR creation with standardized sequential numbering
1 GitHub stars
Michael Nygard format templates for consistent documentation
Full-text search and automated indexing across all decision records
Superseding workflow to maintain a clear chain of architectural evolution
Lifecycle management for proposed, accepted, deprecated, and superseded states

Use Cases

Tracking the rationale behind security and authentication strategies for future audits
Documenting major technology stack choices like databases or frontend frameworks
Managing architectural shifts by formally superseding old patterns with new standards

About

Key Features

Automated ADR creation with standardized sequential numbering
1 GitHub stars
Michael Nygard format templates for consistent documentation
Full-text search and automated indexing across all decision records
Superseding workflow to maintain a clear chain of architectural evolution
Lifecycle management for proposed, accepted, deprecated, and superseded states

Use Cases

Tracking the rationale behind security and authentication strategies for future audits
Documenting major technology stack choices like databases or frontend frameworks
Managing architectural shifts by formally superseding old patterns with new standards