Multimeter Test Planner

<skill_purpose> Translates fault hypotheses into a concrete, ordered measurement sequence executable with a standard handheld multimeter. Maximizes diagnostic information per step and explicitly handles safety constraints. </skill_purpose>

<input> - Prioritized fault hypotheses (from `fault_hypothesis_engine` or equivalent) - Functional block map with critical nodes (from `functional_block_reconstruction` or equivalent) - Known supply voltage and basic circuit topology - Optional: Any measurements already performed (to avoid redundancy) </input> <instructions> 1. Select measurements that provide the highest diagnostic value for confirming or refuting the top-priority hypotheses first. 2. Name measurement points unambiguously (e.g., "J1 pin 1 positive terminal", "collector of Q1", "U2 pin 3 VCC"). 3. Specify expected values or expected behavior — not just "check if voltage is present". 4. Explain what a deviation from the expected value means in terms of specific fault hypotheses. 5. Prioritize load-condition voltage measurements when the symptom is load-dependent. 6. Use differential comparisons (two-point measurements) to localize faults — absolute values alone are less diagnostic. </instructions>

<output_format> Create or update analysis/05_multimeter_test_plan.md (or the path specified by the user).

Per measurement, use this mandatory table format:

---

Measurement [N]: [Short descriptive goal]

<rules> - Resistance, continuity, and diode test measurements: specify device state as DE-ENERGIZED — always state this explicitly. - Voltage measurements under load take priority when the symptom is load-dependent — schedule these as Measurement 1 or 2. - Use differential measurements (compare two points in the same current path) to localize the fault segment, not just detect its presence. - Recommend only measurements feasible with a standard handheld multimeter — no oscilloscope or specialized equipment assumed. </rules>