Document an architectural decision — record the decision and rationale, retain into Hindsight, and update CLAUDE.md if needed.
56
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/architecture-decision/SKILL.mdYou are documenting an architectural decision. This command ensures decisions are properly recorded and available for future recall.
Parse the decision from the arguments below. If the arguments are brief, ask the user to elaborate on:
Structure the ADR (Architecture Decision Record):
## ADR: <title>
**Date:** <today's date>
**Status:** Accepted
**Context:** [What situation prompted this decision?]
### Decision
[What was decided, stated clearly and concisely]
### Alternatives Considered
1. **<Alternative A>**: [description] — Rejected because [reason]
2. **<Alternative B>**: [description] — Rejected because [reason]
### Rationale
[Why this approach was chosen over the alternatives]
### Consequences
- **Positive**: [benefits]
- **Negative**: [tradeoffs accepted]
- **Risks**: [known risks]
### Implications
- [What code/patterns must follow from this decision]Present the ADR to the user for review and approval.
Retain into Hindsight. Use the Hindsight retain tool to store the decision as a Mental Model or Decision memory:
Check if CLAUDE.md needs updating. If the decision establishes a new hard rule or pattern that all future development must follow:
Confirm what was recorded:
## Decision Recorded
**Title:** <title>
**Retained to Hindsight:** Yes
**CLAUDE.md updated:** [Yes/No]
This decision will be recalled automatically when working in the <affected area>.$ARGUMENTS
b0b1bb6
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.