architecture-decisions

Name: architecture-decisions
Availability: InStock
Author: nima

Create and maintain Architecture Decision Records in a consistent, greppable format.

25|3|Updated Jul 14, 2026

Search Tags:#architecture #documentation #adr #engineering #best-practices #decision-record

Ready to run

npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill architecture-decisions-nimadorostkar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decisions
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/development/architecture-decisions
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill architecture-decisions-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of "architectural amnesia," where the reasoning behind critical technical choices is lost over time, leading to confusion and costly re-evaluations.

Core Features & Use Cases

ADR Authoring: Provides a structured, consistent template for documenting Architecture Decision Records.
Trade-off Analysis: Forces the evaluation of options against specific project forces and constraints.
Use Case: When your team is debating whether to switch from a REST API to GraphQL, use this skill to document the forces, the options considered, the final decision, and the long-term consequences.

Quick Start

Use the architecture-decisions skill to draft a new ADR for the proposed migration to a microservices architecture.

Frequently Asked Questions about architecture-decisions

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

FAQPage Schema

How do I document architecture decisions to preserve technical context?▼

Document architecture decisions using Architecture Decision Records (ADRs) to capture forces, options, and consequences in a consistent, greppable format within your repository, preventing architectural amnesia and costly re-evaluations.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) is a structured document that standardizes technical decision context and reasoning. You need an ADR when making complex system design choices like migrating to microservices or switching from REST to GraphQL.

How do I analyze architectural trade-offs for a new system design?▼

Analyze architectural trade-offs by evaluating available options against specific project forces and constraints, ensuring all consequences are documented within the ADR template for consistent long-term reference.

What is the best way to standardize engineering documentation for technical choices?▼

Standardize engineering documentation by drafting ADRs using a consistent template that captures decision context, forces, options, and consequences, ensuring records are greppable and stored directly within the repository.

When should I not use an ADR for architectural decisions?▼

ADRs should not be used for trivial engineering choices that lack meaningful trade-offs or long-term consequences, as the overhead of documenting forces and constraints outweighs the benefit of preserving technical context.

Can I use architecture decision records for a REST to GraphQL migration?▼

Yes, use architecture decision records to document the forces, options considered, final decision, and long-term consequences of switching from REST to GraphQL, ensuring the technical reasoning is preserved for future reference.