bug-interview

Guide a 4-phase triage interview to uncover root causes and write a fix plan.

23|1|Updated Jan 7, 2026

Search Tags:#triage #software-engineering #root-cause-analysis #phased-workflow #bug-interview #investigation-plan

Ready to run

npx skills add https://github.com/neonwatty/claude-skills --skill bug-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-interview
Source: https://github.com/neonwatty/claude-skills/tree/main/skills/bug-interview
Command: npx skills add https://github.com/neonwatty/claude-skills --skill bug-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to conduct a structured bug triage interview that surfaces root causes, reduces ambiguity, and guides subsequent debugging and fixes.

Core Features & Use Cases

Structured Question Rounds: Navigates from initial understanding to in-depth probing, covering reproduction, environment, timing, observed behavior, impact, and isolation.
Synthesis & Plan Output: After gathering sufficient details, produces a concise synthesis and a detailed investigation/fix plan.
Collaborative Dialogue: Maintains a disciplined, question-driven conversation to quickly converge on actionable steps.

Quick Start

Trigger a bug-interview when a bug is reported, then guide the user through the 4 phases (Initial Understanding, Deep Interview, Synthesis, Plan Writing) and save the plan to .claude/plans/bug-<bug-name>.md.

Frequently Asked Questions about bug-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I conduct a structured bug triage to find a root cause?▼

To conduct a structured bug triage, use a 4-phase workflow moving from initial understanding to a deep interview, then synthesis, and finally plan writing to isolate the root cause and document an investigation plan.

What is the best way to investigate a reported software bug without missing details?▼

The best way to investigate a reported software bug is running a categorized interview covering reproduction, environment, timing, observed behavior, impact, and isolation to reduce ambiguity and surface the root cause.

Can I use a phased workflow to create an investigation plan for a complex bug?▼

Yes, you can use a phased workflow to create an investigation plan by progressing through initial understanding and deep interview phases to synthesize findings into a detailed bug fix plan.

How do I document a bug root cause analysis for my engineering team?▼

You document a bug root cause analysis by synthesizing the triage interview details into a structured markdown plan, saving the investigation and fix steps directly to your project plans directory.

What questions should I ask during a software bug investigation?▼

During a software bug investigation, ask categorized questions targeting reproduction steps, environment specs, timing patterns, observed behavior, user impact, prior investigation, and isolation to thoroughly map the issue.

Does structured bug triage work for isolating intermittent software engineering issues?▼

Yes, structured bug triage works for isolating intermittent issues by specifically probing timing and patterns, observed behavior, and isolation conditions to converge on actionable debugging steps.