Tech Lead: Investigate Issue

Prompt file imported from Cataldir/governed-second-brain (.github/prompts/tech-lead-investigate.prompt.md). Copyright stays with the author.

Investigate the reported issue:

1. Symptom Analysis — Restate the problem. Identify affected components and user impact severity.
2. Hypothesis Formation — List the 3 most likely root causes ranked by probability.
3. Evidence Gathering — For each hypothesis, invoke the appropriate specialist agent via #runSubagent to gather evidence:
   • PythonDeveloper — for Python stack traces, async bugs, type errors
   • RustDeveloper — for Rust panics, ownership issues, linker failures
   • TypeScriptDeveloper — for TypeScript type errors, React rendering, bundle issues
   • PlatformEngineer — for CI/CD failures, infrastructure, dependency problems
   • SystemArchitect — for cross-service integration failures, architectural mismatches
4. Root Cause Isolation — Narrow to the confirmed cause. Document the causal chain.
5. Fix Planning — Decompose the fix into agent-assignable tasks. Invoke each specialist via #runSubagent to implement their portion.
6. Prevention — Delegate to PlatformEngineer to recommend test/monitoring additions to prevent recurrence.

Deliver an investigation report with root cause, fix plan, and prevention recommendations.