Babysitter decision-documentation

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

install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/rpikit/skills/decision-documentation" ~/.claude/skills/a5c-ai-babysitter-decision-documentation && rm -rf "$T"
manifest: library/methodologies/rpikit/skills/decision-documentation/SKILL.md
source content

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