Search

PythonReactSEOPDF
GitHub Skill

decision-documentation

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

a5c-ai☆ 417 Repository stars21 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

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

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-03-11
Index updated
2026-03-11
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!