architecture

Capture and rationalize architectural decisions with ADR templates and trade-off analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/filipesf/dotfiles --skill architecture-filipesf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/filipesf/dotfiles/tree/main/agents/skills/architecture
Command: npx skills add https://github.com/filipesf/dotfiles --skill architecture-filipesf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework for architectural decision-making, enabling teams to capture rationale, trade-offs, and ADRs to guide design choices.

Core Features & Use Cases

  • ADR templates and decision framework to capture decisions and rationales
  • Trade-off analysis guidance for selecting patterns and technologies
  • Documentation scaffolding for context discovery, examples, and governance
  • Use Case: When evaluating a major technology shift, use this skill to document decisions, options, and trade-offs for the team.

Quick Start

Start by reviewing context-discovery.md to classify your project, then consult the ADR templates and example decision records to begin documenting your architecture choices.

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 my project?

You document architectural decisions by using ADR templates to capture context, evaluate trade-offs, and record rationale. This structured approach ensures your team understands the reasoning behind system-design choices and technology selections.

What is an ADR and when do I need one for system design?

An ADR, or Architecture Decision Record, is a document that captures the context, options, and trade-offs of a system-design choice. You need one when evaluating major technology shifts to guide and rationalize team decisions.

How do I start evaluating architecture patterns for different deployment scenarios?

Start evaluating architecture patterns by reviewing context discovery to classify your project requirements, then consult trade-off analysis guidance to select appropriate technologies across various deployment scenarios.

Can I use this architecture decision framework for any project scale?

Yes, this architecture decision framework supports project-level architecture work, including requirements analysis and trade-off evaluation, making it suitable for documenting decisions across various deployment scenarios and project scales.

What is the best way to capture rationale for a major technology shift?

The best way to capture rationale for a technology shift is using a structured decision-making framework with ADR templates to document options, evaluate trade-offs, and provide governance scaffolding for your team.