architecture-decision

Generate architecture decision records with numbered templates and decision index updates.

70|42|Updated Mar 27, 2026

Search Tags:#documentation #adr #governance #architecture-decision #technical-decision #decision-index

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill architecture-decision-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents forgotten or undocumented major technology choices by guiding the team through a structured Architecture Decision Record that captures the context, alternatives, and consequences every time a critical decision is made.

Core Features & Use Cases

Guided ADR creation: Determines the next ADR number, gathers context, prompts for missing details, and drafts the full ADR template before saving.
Repository hygiene: Saves the completed ADR under docs/architecture, updates the technical decision index with the new entry, and appends a concise summary to docs/technical/DECISIONS.md.
Use Case: Whenever the team debates a new framework, deployment pattern, or data-storage plan, invoke the skill to ensure the choice and rationale are captured and discoverable across the department.

Quick Start

Ask the skill to capture the upcoming architecture decision, review constraints, and draft the ADR template before saving.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema

How do I document a major technical decision for my repository?▼

To document a major technical decision, you generate an architecture decision record that captures context, alternatives, and consequences, saving it under docs/architecture. This ensures the choice and rationale are captured and discoverable.

What is the best way to maintain a decision index for architecture decisions?▼

The best way to maintain a decision index is to update the index with new entries and append a concise summary to docs/technical/DECISIONS.md whenever an architecture decision record is created, ensuring repository governance and traceability.

When do I need to create an architecture decision record?▼

You need to create an architecture decision record whenever the team debates a new framework, deployment pattern, data-storage plan, or API choice. It prevents forgotten or undocumented major technology choices by capturing the rationale.

How to generate an ADR template with proper numbering and sections?▼

To generate an ADR template, the process determines the next ADR number, gathers context, prompts for missing details, and drafts the full templated sections before saving. It ensures enterprise-grade documentation for significant infrastructure decisions.

Can I use this for enterprise-grade infrastructure and platform decisions?▼

Yes, you can use this for enterprise-grade documentation of significant infrastructure, platform, or API decisions. It applies structured governance by storing ADRs consistently under docs/architecture with traceable decision summaries.

Does this process update the technical decision index automatically?▼

Yes, the process updates the technical decision index with the new entry and appends a concise summary to docs/technical/DECISIONS.md. This maintains repository hygiene and ensures the technical decision is discoverable across the department.