architecture-decision

Name: architecture-decision
Availability: InStock
Author: lekay

Generate Architecture Decision Records with structured sections for status, context, alternatives, and consequences.

Updated May 24, 2026

Search Tags:#technical decision #software project #architecture decision record #collaborative design #adr documentation

Ready to run

npx skills add https://github.com/LeKay/ai-game --skill architecture-decision-lekay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/architecture-decision
Command: npx skills add https://github.com/LeKay/ai-game --skill architecture-decision-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Architecture Decision Records (ADR) by automating documentation, ensuring comprehensive and consistent records of technical decisions.

Core Features & Use Cases

Automated ADR Generation: Quickly create detailed ADRs with structured sections, including status, context, alternatives, and consequences.
Collaborative Decision Making: Facilitates collaborative design and review of ADRs, with integrated checks for architectural coherence and technical feasibility.
Integration with Engine Reference: Ensures ADRs are aligned with engine compatibility and reference documentation.
Use Case: For developers who need to document significant technical decisions in a project, ensuring clarity and traceability for future reference.

Quick Start

Generate an ADR for your next technical decision by running the 'architecture-decision' skill with a title, such as: /architecture-decision my-technical-decision-title.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema

How do I automate Architecture Decision Record documentation for a software project?▼

Automate Architecture Decision Record documentation by running a command with a decision title to generate structured records with sections for status, context, alternatives, and consequences.

What should be included in an ADR for technical decisions?▼

An Architecture Decision Record for technical decisions should include structured sections covering status, context, alternatives, and consequences to ensure clarity and traceability for future reference.

How does collaborative design work with ADR documentation?▼

Collaborative design integrates with ADR documentation by facilitating collaborative review of technical decisions with built-in checks for architectural coherence and technical feasibility.

Do I need engine reference documentation to generate an ADR?▼

Engine reference documentation is required to generate an ADR, ensuring the documented technical decisions align with engine compatibility and reference specifications.

When do I need to create an Architecture Decision Record in software engineering?▼

Create an Architecture Decision Record when you need to document significant technical decisions in a software project, ensuring structured traceability and clarity for future reference.