architecture-tradeoff-analysis
Architecture Tradeoff Analysis
Overview
Use this skill to make architecture choices explicit, comparable, and auditable instead of preference-driven.
Scope Boundaries
- There are several plausible architecture options.
- Decision stakes are high and reversal is expensive.
- Teams need a shared basis for selecting one option.
Core Judgments
- Option quality: whether candidates are realistic for the current context.
- Criteria set: business and technical dimensions that actually drive success.
- Weighting model: which criteria dominate and why.
- Sensitivity: how decision changes when assumptions shift.
Practitioner Heuristics
- Keep criteria small and high-impact; too many criteria hide real priorities.
- Separate hard constraints from weighted preferences.
- Include operational burden and team capability as first-class criteria.
- Document dominant assumptions and the signals that would invalidate them.
Workflow
- Define decision question, constraints, and decision horizon.
- Enumerate candidate options and reject non-viable ones early.
- Set criteria and weighting aligned to current strategy.
- Score options with evidence-backed rationale per criterion.
- Run sensitivity analysis on top-weighted criteria and uncertain assumptions.
- Select preferred option and document fallback decision path.
Common Failure Modes
- Scoring hides biased assumptions rather than exposing them.
- Analysis compares abstract patterns, not implementable options.
- Sensitivity analysis is skipped, leading to brittle conclusions.
Failure Conditions
- Stop when decision criteria cannot be agreed.
- Stop when option scoring lacks evidence for key criteria.
- Escalate when sensitivity analysis shows no robust winner.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9