Decision Record Writing

Name: Decision Record Writing
Availability: InStock
Author: lazyninja435

Document architectural decisions with structured context, alternatives, and rationale.

1|Updated Jun 3, 2026

Search Tags:#architecture #documentation #adr #best-practices #decision-log

Ready to run

npx skills add https://github.com/LazyNinja435/astrai --skill decision-record-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Decision Record Writing
Source: https://github.com/LazyNinja435/astrai/tree/main/.ai/skills/documentation/decision-record-writing
Command: npx skills add https://github.com/LazyNinja435/astrai --skill decision-record-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of tribal knowledge loss by providing a structured, durable format for recording architectural and project decisions, ensuring the rationale behind choices is preserved for future team members.

Core Features & Use Cases

Structured Decision Logging: Enforces a consistent format including context, alternatives, and consequences.
Supersession Tracking: Provides a clear mechanism to mark old decisions as superseded by new ones.
Use Case: When choosing between two database technologies, use this skill to document the pros, cons, and final rationale so that future developers understand why the specific technology was selected.

Quick Start

Use the decision record writing skill to create a new record for the chosen authentication provider based on the provided alternatives.

Frequently Asked Questions about Decision Record Writing

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

FAQPage Schema

What is an architectural decision record and when do I need one?▼

An architectural decision record (ADR) is a standardized document capturing the context, alternatives, and rationale behind a project choice. You need one to preserve architectural rationale and prevent tribal knowledge loss for future team members.

How do I document architectural decisions to ensure long-term project clarity?▼

Document architectural decisions by enforcing a structured format that captures context, alternatives, and consequences. This standardized decision logging ensures long-term project clarity and historical traceability across the team.

How do you track superseded architectural decisions in a decision log?▼

Track superseded architectural decisions by applying specific supersession protocols within the decision log. This mechanism marks old records as superseded by new ones, maintaining decision integrity and historical traceability over time.

What is the best way to standardize project rationale and alternatives documentation?▼

The best way to standardize project rationale is using a write-once file system that enforces specific template structures for documenting alternatives and consequences. This approach ensures consistent decision logging across all architectural choices.

Can I use this decision logging format for choosing between database technologies?▼

Yes, you can use this decision logging format to document choices between database technologies or authentication providers. It captures the pros, cons, and final rationale so future developers understand why the specific technology was selected.