architecture-decision
Document architectural choices
Best use case
architecture-decision is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Document architectural choices
Teams using architecture-decision should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-decision/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-decision Compares
| Feature / Agent | architecture-decision | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Document architectural choices
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Purpose Document architecture decisions with context and rationale using Architecture Decision Records (ADR). ## Usage - `/architecture-decision [topic]` - Document specific architecture decision --- ## Steps 1. **Prompt for decision context:** - What problem are we solving? - What constraints exist? 2. **Gather options considered:** - Option 1: Description, pros/cons - Option 2: Description, pros/cons - Option 3: Description, pros/cons 3. **Document decision made:** - Which option chosen - Why this option - Trade-offs accepted 4. **Link to related context:** - Related projects - Implementation notes 5. **Create ADR document** in 06-Resources/Architecture_Decisions/ --- ## Output Format ```markdown # ADR: [Title] **Date:** [Today] **Status:** Accepted **Deciders:** [Names] ## Context [What problem are we solving? What constraints?] ## Options Considered ### Option 1: [Name] **Pros:** - [Pro 1] **Cons:** - [Con 1] ### Option 2: [Name] [Same structure] ## Decision We chose [Option] because [reasoning]. ## Trade-offs - [Trade-off accepted] ## Implementation Notes [How to implement this decision] ```
Related Skills
architecture-specialist
提供系统架构设计、技术选型、架构审查和组件设计能力。当需要设计新系统、重构现有架构或进行架构审查时使用。
architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
architecture-decision-record
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
alibaba-cloud-architecture
Alibaba Cloud architecture patterns and best practices. Use when designing, deploying, or reviewing infrastructure on Alibaba Cloud including ECS, ACK, Function Compute, and OSS.
5w1h-decision
5W1H Decision Framework Tool. Use for: (1) Systematic decision-making before creating todos, (2) Preventing duplicate implementation, (3) Detecting avoidance behavior, (4) Ensuring agile refactor compliance with executor/dispatcher separation
Tech Stack & Architecture Decision
Define and document the technology stack and architecture decisions for a project. Use when the user needs to choose a tech stack, make architecture decisions, define infrastructure choices, or document technology selections. Triggers on requests like "define the tech stack", "choose technologies", "architecture decisions", "what stack should we use", or any request to select and document frontend, backend, database, auth, hosting, and infrastructure choices for a project.
springboot-architecture-analyzer
系統化分析 Spring Boot 專案並生成完整的企業級架構文件,涵蓋系統概述、架構視圖、技術細節、部署策略等所有關鍵面向。
software-architecture
Design scalable software systems with proven architectural patterns (MVC, microservices, event-driven), SOLID principles, system design trade-offs, and architectural decision records (ADRs).
reviewing-python-architecture
Review ADRs to check they follow testing principles and parent PDR constraints. Use when reviewing ADRs or architecture decisions.
review-architecture
Verify DDD patterns, Clean Architecture boundaries, and bITdevKit-specific conventions in modular monolith projects
react-native-architecture
Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...
react-gradual-architecture
Incremental React code organization guidelines. Start small, then extract when scanning and responsibilities start to blur. Use when creating features, organizing files, refactoring components, or deciding when to extract hooks, UI, or utils.