Individual skill
architecture-decision-record
Document a significant technical decision with its context, alternatives, consequences, and status. Use for: architecture decision record, ADR, technical decision log, technology choice.
.grok/skills/architecture-decision-record/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,223 bytes
Read excerpt
# Architecture Decision Record
## Purpose
Write a concise, durable record of a material technical decision so future contributors can understand the context, trade-offs, and consequences without reconstructing the discussion.
## Workflow
1. Confirm that a real architecture or technology decision is being made; do not create an ADR for routine implementation detail.
2. Assign a stable identifier and a short active-voice title.
3. Describe the context, constraints, decision drivers, and relevant stakeholders.
4. Record the chosen decision precisely, including the intended scope and status: proposed, accepted, deprecated, or superseded.
5. Compare meaningful alternatives and explain the evidence or trade-offs behind the choice.
6. State positive, negative, and neutral consequences, including migration or operational effects.