decision-lifecycle

Name: decision-lifecycle
Availability: InStock
Author: arbiterForge

Author and track numbered, dated architecture decision records with user attribution.

139|7|Updated May 8, 2026

Search Tags:#architecture #adr #governance #audit-trail #decision-records #status-tracking #supersession

Ready to run

npx skills add https://github.com/arbiterForge/codeArbiter --skill decision-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-lifecycle
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/decision-lifecycle
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill decision-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill creates a disciplined, auditable way to capture architecture decisions so teams can record what was decided, why it was decided, and how later decisions supersede it without losing the history.

Core Features & Use Cases

ADR authoring: Creates numbered, dated, user-attributed ADR files in the project decision directory.
Decision tracking: Maintains supersession chains and status history so the current state of a decision is always clear.
Read-only status reporting: Lists ADR health without modifying files, making it safe for review and audit workflows.
Governed change control: Supports decisions that apply to specific file paths so later edits can be checked against recorded architecture rules.

Quick Start

Ask the assistant to record your decision with /adr and provide the title, context, alternatives, and scope so it can author the ADR in the correct numbered file.

Frequently Asked Questions about decision-lifecycle

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

FAQPage Schema

How do I record an architecture decision record with proper traceability?▼

Architecture decision records (ADRs) capture what was decided, why it was decided, and how later decisions supersede it. They maintain an append-only history so teams can trace the context and supersession chain without losing prior rationale.

How does supersession tracking work for outdated ADRs?▼

Supersession tracking maintains explicit chains linking new architecture decision records to the ones they replace. This keeps the current decision state clear while preserving the append-only history of the original ADR files.

How do I generate an ADR status report without modifying files?▼

You can generate an ADR status report through read-only status inspection of your decision directory. This lists ADR health and supersession history safely, making it suitable for audit workflows without modifying any files.

Does this ADR governance approach apply to specific file paths in a repository?▼

Architecture decision records can apply decisions to specific file paths for governed change control. This ensures later repository edits can be checked against the recorded architecture rules and scope defined in the ADR.

What are the limitations of enforcing append-only ADR formatting?▼

Enforcing append-only ADR formatting means you cannot retroactively edit or delete recorded decisions to maintain a strict audit trail. The system enforces canonical formatting and read-only status inspection without guessing missing decision details.