decision-documentation

Solid

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

AI & Automation 1,160 stars 71 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
45
Issue Health 10%
50
License 10%
100
Description 5%
100

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

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

architecture-decision-records

Create and maintain Architecture Decision Records (ADRs) for significant technical choices—frameworks, data stores, API shapes, ML platform decisions. Use when documenting a decision, onboarding, or superseding a prior approach.

15 Updated 2 days ago
charlieviettq
Data & Documents Solid

documentation-and-adrs

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

47,560 Updated 4 days ago
addyosmani
Data & Documents Listed

documentation-and-adrs

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

2 Updated 2 days ago
nota-america
Data & Documents Listed

documentation-and-adrs

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

15 Updated 3 days ago
sampleXbro
AI & Automation Listed

architecture-decision-records

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...

5 Updated today
rootcastleco