skills.rest
fnsalinas
fnsalinasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture

Automate architecture decision documentation and trade-off analysis with ADR templates.

1|Updated Dec 19, 2025
Search Tags:#architecture#documentation#adr#patterns#trade-offs#decision-records
One-click install
npx skills add https://github.com/fnsalinas/fnsalinas.github.io --skill architecture-fnsalinas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/fnsalinas/fnsalinas.github.io/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/fnsalinas/fnsalinas.github.io --skill architecture-fnsalinas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture teams need a reliable, repeatable method to capture requirements, evaluate trade-offs, and document architectural decisions.

Core Features & Use Cases

  • ADR templates and decision records for traceability
  • Requirements capture, trade-off analysis, and pattern references
  • Use cases across project phases from initial design to evolution

Quick Start

Start by articulating the problem, collecting constraints, and drafting an ADR for the key architectural decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema
What are architecture decision records and when do I need them?▼

Architecture decision records (ADRs) document key software design choices and their trade-offs. You need ADRs to ensure traceability and maintainable architecture evolution when making significant design decisions across cross-functional teams.

How do I document architecture trade-offs for a new software project?▼

Document architecture trade-offs by articulating the problem, collecting project constraints, and drafting an ADR. This framework automates requirements analysis and decision documentation to evaluate design patterns systematically.

Does this ADR framework support cross-team collaboration on architecture decisions?▼

Yes, the framework is explicitly designed for cross-team collaboration. It provides standardized ADR templates and pattern references that ensure all stakeholders can trace requirements and evaluate architectural trade-offs together.

What's the best way to capture requirements and analyze trade-offs for architecture evolution?▼

The best way is applying this ADR-guided framework to automate requirements capture and trade-off evaluation. It supports project phases from initial design through architecture evolution using structured decision records.

Can I use ADR templates for pattern references across different project phases?▼

Yes, ADR templates support pattern references throughout project phases. They provide a repeatable structure for documenting architectural decisions from initial design requirements to long-term architecture evolution.

Why should I use ADRs instead of general documentation for software architecture decisions?▼

ADRs provide structured traceability for architectural decisions and trade-offs that general documentation lacks. This framework automates decision record creation and pattern references specifically for maintainable architecture evolution.

Related Skills

Explore More Software Engineering Skills→
petrSimonidesXartpetrSimonidesXart

approach-evaluation

Evaluate technical approaches against project constraints with documented evidence.

Community
Advanced
nishchaydevnishchaydev

architecture

Guide architectural decisions through requirements discovery, trade-off evaluation, and ADR documentation.

Community
Intermediate
stevolandstevoland

adr

Create and manage MADR-compliant Architecture Decision Records across projects.

Community
Basic
senior-sigansenior-sigan

architecture-decision-records

Capture architectural decisions as structured ADR documents with context and rationale.

Community
Advanced