Menu
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | architecture-decision-recorder |
| description | Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale. |
| allowed-tools | ["Read","Write","Edit","Bash","Grep","Glob"] |
Systematically document architectural decisions using the ADR pattern.
# ADR-NNNN: [Title]
**Date:** YYYY-MM-DD
**Status:** [Proposed | Accepted | Deprecated | Superseded]
**Decision Makers:** [Names]
## Context
What is the issue we're trying to solve? What are the forces at play?
### Business Context
- Business goal or requirement
- Constraints (time, budget, team)
- Stakeholder concerns
### Technical Context
- Current system state
- Technical constraints
- Integration requirements
## Decision
We will [decision statement].
### Rationale
Why this approach over alternatives?
## Consequences
### Positive
- Benefit 1
- Benefit 2
### Negative
- Tradeoff 1
- Tradeoff 2
### Risks
- Risk 1 → Mitigation strategy
- Risk 2 → Mitigation strategy
## Alternatives Considered
### Option 1: [Name]
**Pros:** [List]
**Cons:** [List]
**Rejected because:** [Reason]
### Option 2: [Name]
**Pros:** [List]
**Cons:** [List]
**Rejected because:** [Reason]
## Implementation
- [ ] Action item 1
- [ ] Action item 2
## References
- [Link to research]
- [Related ADR]
/adr-create - Create new ADRHelps create, analyze, and maintain Architecture Decision Records
Generates comprehensive API documentation including OpenAPI/Swagger specs, endpoint descriptions, request/response examples, and integration guides. Use when documenting APIs.
Generate complete elizaOS character configurations with personality, knowledge, and plugin setup. Triggers when user asks to "create character", "generate agent config", or "build elizaOS character"
Execute the proper Drizzle Kit workflow for database schema migrations in asset-forge. Use this when the user asks to create a database migration, update the database schema, or when schema changes need to be applied to the database.
Integrates Lighthouse CI for automated performance testing, Core Web Vitals tracking, and regression detection in CI/CD pipelines. Use when user asks to "setup Lighthouse CI", "add performance testing", "monitor Core Web Vitals", or "prevent performance regressions".
Sets up visual regression testing using Percy, Chromatic, or Playwright to catch unintended UI changes through screenshot comparison. Use when user asks to "setup visual testing", "add screenshot tests", "prevent visual bugs", or "setup Percy/Chromatic".