architecture

Document architectural decisions and rationale using ADR templates and guidelines.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/rahlplx/elite-astro-workforce-template --skill architecture-rahlplx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/rahlplx/elite-astro-workforce-template/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/rahlplx/elite-astro-workforce-template --skill architecture-rahlplx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architecture Decision Framework provides a structured approach to documenting architectural decisions, rationale, and trade-offs so teams stay aligned and avoid drift during project evolution.

Core Features & Use Cases

  • ADR templates and guidelines for recording decisions, alternatives, and consequences.
  • Core principles and reading rules to guide architecture discussions and maintain consistency.
  • Use Case: At project kickoff, create ADRs for selected patterns and technologies to capture decisions for long-term maintainability.

Quick Start

Review the ADR guidelines included with this skill, study the example ADRs, and draft an initial ADR for your current design decision.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an ADR and when do I need to document architecture decisions?

An Architecture Decision Record (ADR) captures context, options, decisions, and consequences. You need ADRs during system design sessions or project governance to document trade-offs and prevent team drift as projects evolve.

How do I write an ADR for system design trade-offs?

To write an ADR for system design, use a structured template to record context, alternatives considered, the decision made, consequences, and revisit triggers. This documents trade-offs and captures rationale for project maintainability.

Can I use ADR templates for project kickoff and governance?

Yes, you can use ADR templates at project kickoff to create records for selected patterns and technologies. This provides structured project governance by documenting architectural decisions and rationale for long-term alignment.

What should be included in an architecture decision document?

An architecture decision document should include context, options considered, decisions made, consequences, and revisit triggers. Following these ADR guidelines ensures consistent architecture discussions and rationale tracking.

What is the best way to record architectural alternatives and consequences?

The best way to record architectural alternatives and consequences is using an ADR framework. It provides core principles and reading rules to guide discussions, ensuring trade-offs and decision outcomes are consistently documented.