tradeoff-memo

Generate structured tradeoff memos documenting architectural decisions and engineering rationale.

3|Updated Nov 19, 2025

Search Tags:#architecture #decision making #documentation #ADR #engineering principles #tradeoffs

Ready to run

npx skills add https://github.com/meaganewaller/.dotfiles --skill tradeoff-memo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tradeoff-memo
Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/tradeoff-memo
Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill tradeoff-memo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you meticulously document architectural decisions, ensuring clarity, completeness, and alignment with engineering principles, preventing future confusion and re-litigation of choices.

Core Features & Use Cases

Structured Decision Memos: Generates comprehensive memos covering context, options, tradeoffs, principles, and implications.
Principle Alignment: Encourages tying decisions to established engineering, architectural, and organizational principles.
Use Case: When deciding between two different database solutions, use this skill to document the pros and cons of each, the specific tradeoffs being made (e.g., performance vs. cost), and why a particular choice aligns with the team's long-term goals.

Quick Start

Use the tradeoff-memo skill to document the decision to use microservices over a monolith for the new user authentication system.

Frequently Asked Questions about tradeoff-memo

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

FAQPage Schema

How do I document architectural decisions to prevent future re-litigation?▼

Documenting architectural decisions with structured tradeoff memos prevents re-litigation by capturing context, options considered, explicit tradeoffs, invoked principles, and long-term implications in a clear, auditable format.

What is the best way to write a tradeoff memo for engineering principles?▼

Writing a tradeoff memo for engineering principles involves generating structured documentation that aligns choices with established organizational and architectural rules, ensuring staff-level auditability of long-term implications and explicit tradeoffs.

How do I structure an ADR to compare database solutions or microservices?▼

Structuring an ADR to compare options like database solutions or microservices requires documenting the pros and cons, specific tradeoffs such as performance versus cost, and alignment with long-term team goals within a comprehensive memo.

When do I need to use a structured tradeoff memo for software architecture?▼

You need a structured tradeoff memo for software architecture when making significant decisions, such as choosing microservices over a monolith, to ensure completeness, articulate rationale, and facilitate staff-level auditability of choices.

Can I tie architectural decisions to established engineering principles using an ADR?▼

Tying architectural decisions to established engineering principles using an ADR is supported by generating memos that encourage explicit alignment of choices with organizational and architectural rules for long-term clarity.

Does documenting tradeoffs in a decision memo help with staff-level auditability?▼

Documenting tradeoffs in a decision memo helps with staff-level auditability by providing a structured record of context, options considered, invoked principles, and long-term implications, preventing future confusion.