architecture

Document architectural decisions using ADR templates with context and trade-offs.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/phoenicisf/forex-analyzer --skill architecture-phoenicisf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/phoenicisf/forex-analyzer/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/phoenicisf/forex-analyzer --skill architecture-phoenicisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture teams lack a structured, auditable way to document decisions and trade-offs; this framework provides ADR-based guidance.

Core Features & Use Cases

  • ADR templates and decision records
  • Context analysis, options, trade-offs, and consequences
  • Governance-friendly workflow for design reviews and architecture governance

Quick Start

Summarize the architecture goal for a new project and draft an initial ADR using the provided ADR template.

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 trade-offs for a new project?▼

You document architectural decisions by drafting an Architecture Decision Record (ADR) that captures the context, problem, decision, trade-offs, and consequences. This provides an auditable rationale traceable across design and governance reviews.

What should be included in an ADR template for architecture governance?▼

An ADR template for architecture governance should include sections for context, problem, decision, trade-offs, and consequences. This structure ensures decisions are traceable and auditable during design reviews.

How do I evaluate trade-offs when selecting architecture patterns?▼

You evaluate trade-offs in pattern-selection by documenting each option's context and consequences within an ADR. This framework applies structured analysis to ensure architecture decisions are auditable and justified.

Can I use ADRs for architecture governance and design reviews?▼

Yes, ADRs are designed for architecture governance and design reviews. They provide a structured, auditable workflow to document decisions and capture rationale across review contexts.

What is the best way to maintain an auditable rationale for architecture decisions?▼

The best way to maintain an auditable rationale is using ADR-driven architecture decisions. By documenting context, options, and consequences in decision records, teams ensure traceable choices across governance workflows.

Why do architecture teams need decision records for pattern selection?▼

Architecture teams need decision records because they provide a structured, auditable way to document options and trade-offs. ADRs ensure pattern selection is traceable and justified during design reviews.