decision-documentation
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
Best use case
decision-documentation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
Teams using decision-documentation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/decision-documentation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How decision-documentation Compares
| Feature / Agent | decision-documentation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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`
Related Skills
clinical-documentation-query
Generate compliant physician queries to clarify clinical documentation for accurate coding, severity of illness, and risk of mortality capture
clinical-decision-support-rules
Develop and maintain clinical decision support rules including alerts, reminders, order sets, and evidence-based recommendations within EHR systems
collection-documentation
Create and maintain comprehensive collection records including cataloging, photography, condition documentation, and database management following AAM/ICOM standards
decision-tree-analyzer
Decision tree analysis skill with expected value, risk analysis, and utility theory.
pip-documentation
Create legally compliant performance improvement plan documentation with evidence tracking and milestone management
decision-visualization
Decision-specific visualization skill for creating clear, actionable visual representations of analyses
decision-tree-builder
Automated decision tree construction skill for structuring complex decisions with probabilities, payoffs, and expected value calculations
decision-journal
Decision documentation and learning skill for capturing decision context, rationale, and outcomes
documentation-generator
Generate documentation for migrated systems including API docs, architecture docs, and runbooks
Project Documentation
Generate comprehensive project documentation with source tree analysis and Mermaid diagrams.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)