architecture-decision

Draft ADRs with Context, Decision, Consequences, and GDD mappings.

Updated Apr 25, 2026

Search Tags:#architecture #documentation #adr #governance #software-engineering #gdd

Ready to run

npx skills add https://github.com/packetalien/cursor-game-studios --skill architecture-decision-packetalien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/architecture-decision
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill architecture-decision-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft Architecture Decision Records (ADRs) from user input and project context to capture critical technical decisions, contexts, and trade-offs.

Core Features & Use Cases

Create structured ADRs that document problem statements, decisions, alternatives, consequences, and GDD mappings
Enforce collaborative gates including assumption gathering, stakeholder review, and registry updates
Integrate with GDDs and existing ADRs to maintain traceability and architectural coherence

Quick Start

Provide a short ADR title and any available context to begin drafting the Architecture Decision Record.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema

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

An Architecture Decision Record (ADR) captures critical technical decisions, contexts, and trade-offs. You need to draft an ADR whenever your software project requires documenting a significant architectural choice, its alternatives, and its consequences.

How do I write an Architecture Decision Record with proper context and consequences?▼

Writing an Architecture Decision Record involves a collaborative gate process that gathers assumptions and alternatives. It then drafts complete ADR sections for Context, Decision, Consequences, and GDD mappings to ensure architectural coherence and traceability.

Can I map ADR dependencies to existing Governance Decision Documents?▼

Yes, you can map ADR dependencies to Governance Decision Documents (GDDs). The drafting process ensures traceability to GDDs and existing ADRs, maintaining architectural coherence across the software engineering governance framework.

What is the best way to enforce stakeholder review and assumption gathering for ADRs?▼

The best way to enforce stakeholder review for ADRs is using a collaborative gate process. This process validates drafts with engine specialists and technical direction reviews, ensuring assumptions and stakes are collected before finalizing the registry updates.

Does drafting ADRs require predefined project context and architectural inputs?▼

Yes, drafting ADRs requires available project context and a short ADR title as input. This contextual input is necessary to identify dependencies, map to GDDs, and accurately document the technical decision trade-offs.