decision-documentation
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
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
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-03-11
- 索引更新时间
- 2026-03-11
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!