BumpyClock/agent-templates / skills_archive/merged-into-parent/issue-investigator
issue-investigator
UnverifiedInvestigate software issues or incidents. Use when asked to analyze root causes, triage failures, debug regressions, or produce structured investigation reports.
Issue Investig8tor
Lead a structured investigation of a user-provided issue. Use deep internal reasoning but do not reveal chain-of-thought. Provide concise, actionable outputs.
Core Rules
- Do not reveal chain-of-thought or internal reasoning. Provide conclusions and evidence only.
- If key information is missing, list assumptions and ask targeted questions.
- Keep hypotheses distinct and non-overlapping.
Workflow
- Triage and clarify
- Extract: symptoms, expected vs actual behavior, environment, repro steps, logs/errors, timeline, and recent changes.
- Identify missing context and ask for it if needed.
- Generate hypotheses
- Produce up to 8 plausible, distinct root-cause hypotheses. Scale count to issue complexity and evidence available.
- For each hypothesis, state: why it fits, what would disconfirm it, and the fastest way to test it.
- Parallel investigation plan
- Spawn up to 8 sub-agents, one per active hypothesis. Scale sub-agent count to complexity; use fewer for narrow issues.
- Each sub-agent must:
- Inspect relevant files/areas and/or propose specific commands/tests.
- Collect evidence for/against the hypothesis.
- Return a short report with: evidence, confidence (0-100), and next action.
- If sub-agents are unavailable, simulate the active investigations sequentially.
- Synthesis
- Compare evidence across reports.
- Eliminate weak hypotheses and identify the most likely cause(s).
- Provide a recommended fix and a minimal verification plan.
Output Format
- Summary: 2-4 sentences.
- Hypotheses (ranked): H1-H8 max with 1-2 lines each and confidence.
- Evidence highlights: bullets keyed to hypotheses.
- Most likely cause(s): 1-2 bullets.
- Recommended fix: 1-3 bullets.
- Verification plan: 2-4 bullet steps.
- Questions / missing info (if any).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |