deep153 Triage Issue
Investigate a reported problem, find its root cause. Prefer action over questions: minimize back-and-forth with the user.
Process
1. Capture the problem
Get a brief description of the issue from the user. If they have not provided one, ask a single question: "What is the problem you are seeing?"
Do not ask follow-up questions yet. Start investigating immediately.
2. Explore and diagnose
Use deep codebase investigation (for example the Task tool with subagent_type: "explore", or equivalent search and reads) to find:
- Where the bug manifests (entry points, UI, API responses)
- What code path is involved (trace the flow)
- Why it fails (the root cause, not only the symptom)
- What related code exists (similar patterns, tests, adjacent modules)
Look at:
- Related source files and their dependencies
- Existing tests (what is covered, what is missing)
- Recent changes to affected files (
git logon relevant paths) - Error handling on the code path
- Similar patterns elsewhere that behave correctly
3. Identify the fix approach
From the investigation, determine:
- The minimal change that addresses the root cause
- Which modules or interfaces are affected
- Which behaviors must be verified with tests
- Whether this is a regression, missing behavior, or design flaw
4. Google log analysis
## Problem
A clear description of the bug or issue, including:
- What happens (actual behavior)
- What should happen (expected behavior)
- How to reproduce (if applicable)
## Root Cause Analysis
What the investigation showed:
- The code path involved
- Why the current code fails
- Contributing factors
Do not anchor this section to brittle details: avoid exact file paths, line numbers, or layout-specific implementation notes. Prefer modules, behaviors, and contracts so the issue stays useful after refactors.
## Examples
**User:** "Checkout fails when cart has a gift card."
**You:** Explore cart and checkout flows, find root cause, if required search google logs and provide the analysis summary. Keep it easy to understand.
**User:** "Triage CORE-1234" (with enough context in thread)
**You:** Same workflow using thread context as the problem statement.