# Decision Documentation

> Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.

- Skill: `majiayu000/decision-documentation` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/decision-documentation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/decision-documentation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/decision-documentation

---


# Decision Documentation

## Overview

Document significant architectural and technical decisions as Architecture Decision Records (ADRs). Can be invoked at any point during the RPI workflow.

## When to Use

- Making a significant architectural choice
- Choosing between competing approaches
- Documenting a decision for future reference
- Recording rationale that would otherwise be lost

## ADR Format

- **Title**: Clear description of the decision
- **Status**: Proposed, Accepted, Deprecated, Superseded
- **Context**: Why this decision is needed
- **Options**: Alternatives considered with pros/cons
- **Decision**: The chosen option with rationale
- **Consequences**: Expected positive and negative outcomes

## Output

ADRs are written to `docs/decisions/` with sequential numbering (e.g., `0001-use-typescript.md`).

## Tool Use

Invoke via babysitter process: `methodologies/rpikit/rpikit-decision`