skills.rest
TraftG
TraftGCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision

Generate ADR-XXXX files with Context, Decision, Consequences, and Alternatives sections.

33|8|Updated Mar 26, 2026
Search Tags:#documentation#codebase#adr#software-engineering#architecture-decision#decision-record#design-choices
One-click install
npx skills add https://github.com/TraftG/opencode-game-studio --skill architecture-decision-traftg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/TraftG/opencode-game-studio/tree/main/.opencode/skills/architecture-decision
Command: npx skills add https://github.com/TraftG/opencode-game-studio --skill architecture-decision-traftg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing significant technical decisions without a structured, discoverable record leads to inconsistencies, knowledge loss, and replay of past debates.

Core Features & Use Cases

  • Create Architecture Decision Records (ADRs) for major technical choices to document context, alternatives, and consequences.
  • Automatically assign the next ADR number by scanning the docs/architecture/ directory, accumulate related context, and provide a reusable ADR template.
  • Guide users through decisions by prompting clarifying questions, generate ADRs in the prescribed ADR-XXXX format, and store them in the codebase for traceability.

Quick Start

Create a new ADR by answering prompts and save it to docs/architecture/adr-XXXX-Title.md.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I document architecture decisions in a codebase?▼

You document architecture decisions by creating an Architecture Decision Record (ADR) that captures context, alternatives, and consequences. This Skill generates ADRs in the ADR-XXXX format and stores them under docs/architecture/ for codebase traceability.

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

An Architecture Decision Record (ADR) is a structured document that captures major technical choices, their context, and consequences. You need an ADR to prevent knowledge loss and avoid replaying past debates when making significant software engineering decisions.

How do I automatically number ADRs in an existing project?▼

Automatically number ADRs by scanning the docs/architecture/ directory for existing records and parsing their numeric identifiers. This identifies the next sequential ADR number to assign to your new decision record.

What context should I gather before writing an ADR?▼

Gather context by reviewing related code, existing ADRs in the docs/architecture/ directory, and project requirements. This accumulated context informs the decision and populates the Context and Alternatives sections of the ADR template.

Can I create ADRs without manually setting up a template?▼

Yes, you can create ADRs without manual setup. The Skill provides a reusable ADR template, prompts clarifying questions to guide your decision, and automatically saves the formatted document to the correct architecture directory.

Related Skills

Explore More Software Engineering Skills→
xxihxxih
1

architecture-decision-records

Capture architecture decisions as structured ADR documents in docs/adr.

Community
Intermediate
sddevelopment-besddevelopment-be
13

ARCHITECT ADR

Generate Proposed ADR Markdown files with decision sections and impact matrices.

Official
Advanced
alexandremendoncaalvaroalexandremendoncaalvaro
1

ad-drift

Detect discrepancies between repository documentation and actual codebase implementation.

Community
Intermediate
wanghaishengwanghaisheng
10

architecture-decision

Generate Architecture Decision Records documenting context, alternatives, and consequences.

Community
Intermediate