| name | deep-investigation |
| description | Investigate an operational problem to determine what happened, assess its impact, and recommend next steps using a hypothesis-backed approach. |
Evidence-Backed Investigation
Investigate an operational problem using relevant evidence to explain what happened, assess the impact, and identify useful next steps.
Procedure
1. Understand the request
Scan the conversation for:
- The reported symptom or unexpected behavior
- The affected service, environment, region, or workflow
- The relevant timestamps or time range
- Links to external context
- What the user needs to decide or do
Use available context first. Fetch additional context when it can change the conclusion or next action.
Perform a quick scan using available tools to determine if the problem is related to a recent, ongoing incident.
2. Generate hypotheses
After identifying what went wrong, generate 2-4 plausible root-cause hypotheses. Each must include:
- A short label
- Why the hypothesis is plausible based on the available context
- The signals that can validate or invalidate it
Prioritize the most plausible hypotheses and the signals most likely to distinguish between them.
3. Validate hypotheses and determine what happened
Investigate each hypothesis using the hypothesis-validation skill. For each hypothesis, determine whether it is validated, invalidated, or inconclusive and explain the conclusion with specific evidence.
Establish:
- What changed or failed
- When it started
- Whether it is ongoing, recovering, or resolved
- Which explanation is best supported by the evidence
Do not require a validated root cause. Clearly distinguish observed facts, supported explanations, and unknowns.
Record findings as you validate. Follow the Evidence rules in the agent instructions. Call , , and as those rules say.
