technical-case-diagnosis

name	technical-case-diagnosis
description	Diagnose a complex support case by reconstructing environment, configuration, timeline, logs, network, dependencies, and reproduction evidence before assigning cause.

Technical Case Diagnosis

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using customer steps, environment/version data, logs, config with secrets redacted, network evidence, and timestamps. Do not fill material gaps with assumptions when they can change the result.
3. Normalize the symptom, capture versions/topology, reproduce or bracket conditions, correlate logs/traces, test competing hypotheses, and isolate the first divergence.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The case has a reproducible or strongly evidenced causal classification and unsafe guesses are explicitly rejected.