Scheduled upgrade in progress. Some pages may load slowly or ask you to retry.

Decision Documentation

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

majiayu000 a175199 2 files · 2.1 KB Updated 567 repo stars

File contents

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

majiayu000/claude-skill-registry-data/tree/main/documents/decision-documentation commit a17519904e

Frequently asked questions

npx skillmds add majiayu000/decision-documentation