How do I install the Architecture Decision skill?

Run npx skillmds add majiayu000/architecture-decision-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Decision safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Decision?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Decision free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture Decision?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Decision by majiayu000

Name: Architecture Decision
Rating: 4.2 (5 reviews)
Author: majiayu000

Architecture Decision

Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.

majiayu000 63e6cba 2 files · 3.3 KB Updated Sep 9, 2026 567 repo stars

File contents

When this skill is invoked:

Determine the next ADR number by scanning docs/architecture/ for existing ADRs.
Gather context by reading related code and existing ADRs.
Guide the user through the decision by asking clarifying questions if the title alone is not sufficient.
Generate the ADR following this format:

# ADR-[NNNN]: [Title]

## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-XXXX]

## Date
[Date of decision]

## Context

### Problem Statement
[What problem are we solving? Why does this decision need to be made now?]

### Constraints
- [Technical constraints]
- [Timeline constraints]
- [Resource constraints]
- [Compatibility requirements]

### Requirements
- [Must support X]
- [Must perform within Y budget]
- [Must integrate with Z]

## Decision

[The specific technical decision made, described in enough detail for someone
to implement it.]

### Architecture Diagram
[ASCII diagram or description of the system architecture this creates]

### Key Interfaces
[API contracts or interface definitions this decision creates]

## Alternatives Considered

### Alternative 1: [Name]
- **Description**: [How this would work]
- **Pros**: [Advantages]
- **Cons**: [Disadvantages]
- **Rejection Reason**: [Why this was not chosen]

### Alternative 2: [Name]
- **Description**: [How this would work]
- **Pros**: [Advantages]
- **Cons**: [Disadvantages]
- **Rejection Reason**: [Why this was not chosen]

## Consequences

### Positive
- [Good outcomes of this decision]

### Negative
- [Trade-offs and costs accepted]

### Risks
- [Things that could go wrong]
- [Mitigation for each risk]

## Performance Implications
- **CPU**: [Expected impact]
- **Memory**: [Expected impact]
- **Load Time**: [Expected impact]
- **Network**: [Expected impact, if applicable]

## Migration Plan
[If this changes existing code, how do we get from here to there?]

## Validation Criteria
[How will we know this decision was correct? What metrics or tests?]

## Related Decisions
- [Links to related ADRs]
- [Links to related design documents]

Save the ADR to docs/architecture/adr-[NNNN]-[slug].md.

---name: architecture-decision-2description: Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.--- When this skill is invoked: 1. **Determine the next ADR number** by scanning `docs/architecture/` for existing ADRs. 2. **Gather context** by reading related code and existing ADRs. 3. **Guide the user through the decision** by asking clarifying questions if the title alone is not sufficient. 4. **Generate the ADR** following this format: ```markdown # ADR-[NNNN]: [Title] ## Status [Proposed | Accepted | Deprecated | Superseded by ADR-XXXX] ## Date [Date of decision] ## Context ### Problem Statement [What problem are we solving? Why does this decision need to be made now?] ### Constraints - [Technical constraints] - [Timeline constraints] - [Resource constraints] - [Compatibility requirements] ### Requirements - [Must support X] - [Must perform within Y budget] - [Must integrate with Z] ## Decision [The specific technical decision made, described in enough detail for someone to implement it.] ### Architecture Diagram [ASCII diagram or description of the system architecture this creates] ### Key Interfaces [API contracts or interface definitions this decision creates] ## Alternatives Considered ### Alternative 1: [Name] - **Description**: [How this would work] - **Pros**: [Advantages] - **Cons**: [Disadvantages] - **Rejection Reason**: [Why this was not chosen] ### Alternative 2: [Name] - **Description**: [How this would work] - **Pros**: [Advantages] - **Cons**: [Disadvantages] - **Rejection Reason**: [Why this was not chosen] ## Consequences ### Positive - [Good outcomes of this decision] ### Negative - [Trade-offs and costs accepted] ### Risks - [Things that could go wrong] - [Mitigation for each risk] ## Performance Implications - **CPU**: [Expected impact] - **Memory**: [Expected impact] - **Load Time**: [Expected impact] - **Network**: [Expected impact, if applicable] ## Migration Plan [If this changes existing code, how do we get from here to there?] ## Validation Criteria [How will we know this decision was correct? What metrics or tests?] ## Related Decisions - [Links to related ADRs] - [Links to related design documents] ``` 5. **Save the ADR** to `docs/architecture/adr-[NNNN]-[slug].md`.

Frequently asked questions