skills.rest
jwilger
jwilgerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decisions

Manage Architecture Decision Records and maintain living architecture documentation.

Updated Jul 1, 2026
Search Tags:#design#architecture#documentation#decisions#adr#governance
One-click install
npx skills add https://github.com/jwilger/eventcore --skill architecture-decisions-jwilger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decisions
Source: https://github.com/jwilger/eventcore/tree/main/.agents/skills/architecture-decisions
Command: npx skills add https://github.com/jwilger/eventcore --skill architecture-decisions-jwilger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all significant architectural decisions are documented before implementation, preventing architectural drift and maintaining a clear understanding of the system's design rationale.

Core Features & Use Cases

  • ADR Recording: Guides the creation of Architecture Decision Records (ADRs) using a standardized format.
  • Living Architecture: Facilitates the maintenance of a central ARCHITECTURE.md document.
  • Decision Governance: Implements a process for reviewing and approving architectural changes.
  • Use Case: When considering a new database technology, this Skill will prompt for the ADR context, alternatives, decision, and consequences, ensuring the choice is well-reasoned and recorded.

Quick Start

Use the architecture-decisions skill to record a new decision about the primary database technology.

Frequently Asked Questions about architecture-decisions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural decisions to prevent architectural drift?▼

You can document architectural decisions using Architecture Decision Records (ADRs) to capture context, alternatives, and consequences. This prevents drift by ensuring significant choices are recorded before implementation begins.

What is the best way to manage technology stack choices and integration pattern selection?▼

Managing technology stack choices requires a systematic decision-making process that defines domain boundaries and integration patterns. Using ADR-as-PR workflows enforces architectural alignment and governance during these selections.

How do I maintain living architecture documentation alongside my codebase?▼

Living architecture documentation is maintained through a central ARCHITECTURE.md file. This document is updated systematically as decisions evolve, providing a clear understanding of the system's design rationale.

Do I need an ADR workflow for every code change in my software engineering project?▼

An ADR workflow is not needed for every code change. Architecture Decision Records are specifically for significant architectural decisions, such as choosing a new database technology or defining domain boundaries, not routine modifications.

Can I enforce architectural alignment during implementation using ADRs?▼

Yes, architectural alignment is enforced during implementation by adopting an ADR-as-PR workflow. This process ensures that all proposed architectural changes are reviewed and approved before they are merged.

Related Skills

Explore More Software Engineering Skills→
lozitlozit
2

add-adr

Create Architecture Decision Records and update the project ADR index.

Community
Intermediate
superdesigndevsuperdesigndev
43

archlet

Generate interactive architecture maps and PR diff overlays from import graphs.

Official
Advanced
iamacoffeepotiamacoffeepot
1

review

Automate code review for Aether engine PR-bound changes.

Community
Intermediate
sddevelopment-besddevelopment-be
13

Decision-First Development Workflow

Capture architectural decisions and rationale in traceable ADR-aligned workflows.

Official
Advanced