adr-maintenance

Name: adr-maintenance
Availability: InStock
Author: kristopherlb

Create and maintain architecture decision records with context, tradeoffs, and verification details.

Updated Feb 15, 2026

Search Tags:#architecture #software engineering #documentation #adr #verification #decision records

Ready to run

npx skills add https://github.com/Kristopherlb/shinobi-wan --skill adr-maintenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-maintenance
Source: https://github.com/Kristopherlb/shinobi-wan/tree/main/.cursor/skills/adr-maintenance
Command: npx skills add https://github.com/Kristopherlb/shinobi-wan --skill adr-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents architecture decisions from becoming undocumented or ambiguous by creating structured records with context, tradeoffs, evidence, and follow-up actions.

Core Features & Use Cases

ADR Creation and Updates: Draft and maintain architecture decision records with consistent status, context, consequences, and verification details.
Decision Traceability: Link decisions to implementation files, tests, and reproducible verification evidence.
Use Case: When changing Shinobi architectural boundaries or behavior contracts, use this Skill to document the decision and preserve the reasoning behind the change.

Quick Start

Use the adr-maintenance skill to create or update an architecture decision record for the specified decision and affected packages.

Frequently Asked Questions about adr-maintenance

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

FAQPage Schema

How do I document architecture decisions with traceable evidence?▼

You can document architecture decisions by creating structured architecture decision records that capture context, tradeoffs, consequences, and reproducible verification commands. This ensures your software architecture changes remain clear and traceable over time.

What is an architecture decision record used for in software engineering?▼

An architecture decision record is used to prevent architectural decisions from becoming undocumented or ambiguous. It provides a structured entry containing the context, tradeoffs, and follow-up tracking needed to preserve the reasoning behind package boundary updates and behavior contract changes.

How do I maintain decision traceability when updating package boundaries?▼

To maintain decision traceability when updating package boundaries, you use structured records to link the architectural decisions directly to implementation files, tests, and verification evidence. This preserves the reasoning and ensures behavior contract changes are fully documented.

What should be included in a structured architecture decision record?▼

A structured architecture decision record should include the decision context, tradeoffs, consequences, verification commands, implementation links, and follow-up tracking. These entries ensure that architectural changes and their supporting evidence remain clear and traceable.

When do I need to create an architecture decision record?▼

You need to create an architecture decision record when making software architecture changes, updating package boundaries, or modifying behavior contracts that require traceability. It documents the decision and preserves the supporting evidence and reasoning behind the change.

Can I update existing architecture decision records without losing previous context?▼

Yes, you can update existing architecture decision records without losing previous context by maintaining consistent status entries. The records are designed to be drafted and updated while preserving the original context, tradeoffs, and verification details throughout the software lifecycle.