architecture-decision

<!-- Generated from `.claude/skills/_available/engineering/architecture-decision/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> # Architecture decision ## When to use Use this skill when a material architecture choice, constraint, or reversal needs a traceable Architecture Decision Record (ADR), or when an existing ADR's state and rationale need review. Do not use it for live incident response, implementation instructions that do not require a design decision, or a decision that has no identifiable evidence or human decision authority. Not for silently choosing on behalf of the team or rewriting historical ADRs. ## Inputs and source discipline Start with the decision question, scope, constraints, affected systems, decision authority, and intended decision window. Treat a missing authority, constraint, or date as unknown; ask for it or mark it TBD. Build a source ledger before comparing options. For every material claim record the source, source date, as-of date/time, locator, and freshness or access limitation. Prefer directly inspected code, configuration, tests, measured operations, and dated requirements; label meeting recollections and interpretations accordingly. Keep conflicting sources linked rather than silently choosing one. ## Method 1. Read the relevant context in read-only mode. State the problem, desired outcome, non-negotiable constraints, decision deadline if evidenced, and what is outside scope. 2. Enumerate the status quo an...