engineering-wisdom

# Engineering Wisdom Give practical advice without treating a school of thought as universal law. Repository intent, code, tests, and observed behavior remain authoritative. ## Establish Scope 1. Read `AGENTS.md`, `docs/WORKFLOW.md`, and only the repository material relevant to the request. 2. Confirm that the user explicitly invoked this skill. Installation alone is not activation. 3. Determine whether the request is advice/review or an authorized change. Keep reviews read-only. For changes, follow repository authority and validation rules before editing. 4. Read [references/heuristics.md](references/heuristics.md). Select only heuristics that match observed evidence. Read [references/sources.md](references/sources.md) when attribution or the intellectual basis matters. 5. When the request crosses a host boundary, inspect the composition root, external input, adapter semantics, shipped artifact, and cumulative state that are relevant. Do not assume isolated core tests prove those boundaries. ## Review From Evidence For each material finding, keep these fields separate: - **Observation:** A concrete repository fact with a path, symbol, test, command result, or behavior. - **Heuristic:** One named rule of thumb from the catalog and why it may apply. - **Trade-off:** Counter-pressure, cost, or a condition under which following the heuristic would make the system worse. - **Proposed repository-owned enforcement:** Either `None`, or a separate...