architecture-decision

Generate Architecture Decision Records with context, constraints, and alternatives.

Updated Mar 15, 2026

Search Tags:#architecture #adr #decision-making #software-design #architecture-decision #design-documentation

Ready to run

npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill architecture-decision-jtvaris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/architecture-decision
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill architecture-decision-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates Architecture Decision Records (ADRs) to document significant technical decisions, their context, constraints, alternatives considered, and consequences, ensuring traceability of architectural choices.

Core Features & Use Cases

ADR generation: Create ADRs that capture the decision, context, constraints, and alternatives.
Context gathering: Collect related code, ADRs, and design notes to inform the decision.
Guided decision process: Interact with users to clarify titles and surface required details.
Use Case: When a major technical choice requires formal documentation for accountability and future reference.

Quick Start

Provide a title for the ADR and the assistant will scaffold a complete ADR draft.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema

How do I create an Architecture Decision Record for a major software design choice?▼

To create an Architecture Decision Record, you provide a title and the assistant scaffolds a complete ADR draft. It guides you through gathering context, constraints, and alternatives to document the technical decision.

What is an ADR and when do I need to document architectural decisions?▼

An ADR is a design document that captures significant technical decisions, their context, constraints, and consequences. You need ADRs when major architectural choices require formal documentation for accountability and traceability.

How do I document context and alternatives considered for a software architecture decision?▼

You document context and alternatives by interacting with the assistant to surface required details. It collects related code, existing ADRs, and design notes to inform the decision and generate the structured ADR content.

What is the best way to automate ADR numbering and formatting for engineering teams?▼

The best way to automate ADR formatting is using a guided assistant that determines the next ADR number and generates content in a standard ADR format. This includes title, status, date, context, constraints, and alternatives.

Does this ADR generation process require any specific frameworks or dependencies?▼

No specific frameworks or dependencies are required to generate ADRs. The process operates independently by gathering context and guiding you through the decision to output the final architecture decision record.

Can I use this to capture consequences and constraints for technical decisions?▼

Yes, you can capture consequences and constraints for technical decisions. The generated ADR explicitly includes sections for context, constraints, alternatives considered, and the resulting consequences of the architectural choice.