architecture

Document architectural decisions with ADR templates and rationale.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill architecture-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/oalansilva/crypto/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/oalansilva/crypto --skill architecture-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This framework guides teams to analyze requirements, evaluate trade-offs, and capture the rationale behind architectural decisions.

Core Features & Use Cases

  • ADR templates and decision records for consistent documentation
  • Requirements analysis and trade-off evaluation to guide design decisions
  • Reusable guidelines and prompts for design reviews and knowledge transfer

Quick Start

Start a new ADR by outlining the problem, listing alternatives, and selecting a design with rationale.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architectural decisions and their rationale?

You document architectural decisions using structured ADR templates that capture trade-offs, constraints, and outcomes. This framework enforces discovery prompts and checklists to ensure the traceability and reproducibility of your design choices across projects and teams.

What is the best way to evaluate trade-offs during software design sessions?

Evaluating trade-offs during design sessions requires applying a structured framework to analyze requirements and list alternatives. This approach captures the specific rationale behind your architectural decisions to guide future design reviews and knowledge transfer.

How do I start an Architecture Decision Record for a new project?

To start an Architecture Decision Record, you outline the problem, list alternatives, and select a design with rationale. The framework provides reusable guidelines and prompts to structure this requirements analysis and trade-off evaluation.

Can I use this ADR framework to ensure consistency across multiple teams?

Yes, you can use this ADR framework to ensure consistency across multiple teams. It provides reusable guidelines and enforces ADR templates across real-world design sessions, capturing trade-offs and outcomes for reliable knowledge transfer.

Why does my team struggle with the traceability of architecture decisions?

Teams struggle with traceability when they lack enforced ADR templates and discovery prompts. Without a structured framework to document constraints and outcomes, the rationale behind architectural decisions becomes difficult to reproduce.