architecture

Document architectural decisions using ADR templates and trade-off analysis.

3|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/grasberg/sofia --skill architecture-grasberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/grasberg/sofia/tree/main/cmd/sofia/internal/onboard/antigravity-kit/.agent/skills/architecture
Command: npx skills add https://github.com/grasberg/sofia --skill architecture-grasberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making requires structured reasoning, traceable trade-offs, and documented rationale to guide design choices across teams.

Core Features & Use Cases

  • ADR templates and decision records to capture context, options, and trade-offs for significant architecture decisions.
  • Context discovery and validation checklists to align stakeholders and reduce scope creep.
  • Reusable patterns and reference materials to accelerate design discussions and ensure consistency.

Quick Start

Start by documenting a new architecture decision using context, options, and ADR results to capture rationale and trade-offs.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an architectural decision record and when do I need one?

An architectural decision record (ADR) is a structured document that captures context, options, and trade-offs for significant architecture decisions. You need one to provide traceable rationale and guide design choices across teams.

How do I document architectural trade-offs for my project?

Document architectural trade-offs by applying ADR templates and context discovery checklists to evaluate options. This codifies the rationale behind design choices, ensuring versioned architecture records and traceable decisions across teams.

Can I use ADR templates for small projects or are they only for large teams?

You can use ADR templates for projects of all sizes requiring traceable design decisions. The framework applies structured reasoning and documented rationale to guide choices regardless of your team's scale.

What is the best way to align stakeholders and reduce scope creep during architecture design?

The best way to align stakeholders is using context discovery and validation checklists during architectural decision-making. This structured reasoning ensures documented rationale and traceable trade-offs guide design choices.

Does this framework provide reusable patterns for architecture decision-making?

Yes, the framework provides reusable patterns and reference materials to accelerate design discussions. These patterns ensure consistency in architectural decision-making and offer structured reasoning for trade-off analysis.

Why should I use structured rationale instead of informal architecture documentation?

Structured rationale provides traceable trade-offs and versioned architecture records that informal documentation lacks. This structured reasoning ensures design choices are documented, validated, and accessible to guide teams across projects.