feature-troubleshoot

# Troubleshooting Command

You are executing the **SYSTEMATIC TROUBLESHOOTING** workflow - a methodical debugging process that prevents spinning wheels through hypothesis-driven investigation.

## Contents

- [Problem Context](#problem-context)
- [What Makes This Different](#what-makes-this-different)
- [Workflow Overview](#workflow-overview)
- [Phase Details](#phase-details)
- [Ask For Help Mechanism](#ask-for-help-mechanism)
- [Error Handling](#error-handling)

---

## Problem Context

$ARGUMENTS

If no specific problem was provided above, you will help the user define the problem clearly.

---

## What Makes This Different

**Ad-hoc debugging**: Try things randomly, hope something works
**Systematic troubleshooting (this command)**: Form hypotheses, gather evidence, verify fixes

**Key capability**: "Something is broken" → investigate → "Root cause identified and fixed"

This provides structured debugging rather than trial and error.

### Relationship to Feature-Audit

| Command | Mode | Purpose |
|---------|------|---------|
| `/feature-audit` | Proactive | "Verify this works as expected" |
| `/feature-troubleshoot` | Reactive | "This is broken, help me fix it" |

Both complement each other - audit can prevent issues, troubleshoot resolves them.

---

## Workflow Overview

This command orchestrates a 5-phase workflow:

| Phase | Name | Purpose |
|-------|------|---------|
| 1 | Problem Definition | Clearly define what's wrong and expected behavior |
| 2 | Hypothesis Formation | Generate possible causes ranked by likelihood |
| 3 | Investigation | Gather evidence to test hypotheses |
| 4 | Resolution | Apply fix based on evidence |
| 5 | Verification | Confirm the fix works and problem is resolved |

---

## Phase Details

### Phase 1: Problem Definition

**See**: [problem-definition.md](problem-definition.md)

- Gather problem details from user
- Establish expected vs actual behavior
- Identify when the problem started (if known)
- Document reproduction steps
-