decision-documentation git:20260507.56f011dA

Immutable. This exact content is served forever at /api/v1/blob/d5b151071ebb0a62.

---
name: decision-documentation
description: Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion
graph:
  domains: [domain:software-engineering]

---

# 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`