robotics-bringup-diagnostician

name	robotics-bringup-diagnostician
description	Diagnose why a robot software stack will not bring up cleanly across environment, launch, hardware, and runtime dependencies. Use when robot bringup fails or stalls.

Robotics Bringup Diagnostician

Overview

Diagnose why a robot software stack will not bring up cleanly across environment, launch, hardware, and runtime dependencies.

Core Workflow

1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
2. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
3. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
4. Validate the explanation with the smallest reliable check the repo or environment supports.

Deliver

• A concise diagnosis with the most likely root cause or bounded uncertainty.
• The highest-signal evidence and suspect files, configs, or systems involved.
• The smallest safe fix path or next experiment to run.

Guardrails

• Do not claim a root cause without evidence that explains the observed behavior.
• Separate symptoms from likely causes and call out uncertainty explicitly.
• Prefer the smallest reproducible scope before escalating to broad changes.
• Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.