Architecture Decisions Skill
Auto-activated when user asks to create ADRs, document decisions, or "create an ADR".
Purpose
Helps teams document architecture decisions using Architecture Decision Records (ADRs), ensuring decisions are captured with context, alternatives, and consequences.
Activation Triggers
- •"Create an ADR"
- •"Document this decision"
- •"Architecture decision record"
- •"Document technical decision"
Output
Provides:
- •ADR template
- •Decision structure
- •Context capture
- •Alternatives analysis
- •Consequences documentation
Connected To
- •Section 4: System Architecture & Design
- •Section 13: Lessons Learned & Continuous Improvement
- •docs/adr/ directory
ADR Template
When activated, provides structured ADR template:
markdown
# ADR [Number]: [Decision Title] Status: [Proposed / Accepted / Deprecated / Superseded] Date: [Date] Deciders: [Names] Consulted: [Names] Informed: [Names] ## Context [What is the issue we're seeing?] ## Decision [What is the change we're proposing?] ## Consequences Positive: - [Benefit 1] - [Benefit 2] Negative: - [Trade-off 1] - [Trade-off 2] ## Alternatives Considered 1. [Alternative 1] - Pros: [List] - Cons: [List] - Why not chosen: [Reason]
Usage
Ask: "Create an ADR for [decision description]"
The skill will:
- •Generate ADR number
- •Guide through context capture
- •Help document decision
- •Analyze alternatives
- •Save to docs/adr/ directory