decision-documentation

Solid

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

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
97
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

Related Skills