ferrox-debug

name	ferrox-debug
description	Something is broken, failing, crashing or behaving wrong. Investigates and survives /clear
argument-hint	[list | status <slug> | continue <slug> | --diagnose] [issue description]
allowed-tools	["Read","Write","Bash","Agent","AskUserQuestion"]

Debug issues using scientific method with subagent isolation.

Orchestrator role: Gather symptoms, spawn ferrox-debugger agent, handle checkpoints, spawn continuations.

Flags:

• --diagnose — Diagnose only. Returns a Root Cause Report without applying a fix.

Subcommands: list · status <slug> · continue <slug>

<available_agent_types> Valid Ferrox subagent types (use exact names — do not fall back to 'general-purpose'):

• ferrox-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
• ferrox-debugger — investigates bugs using scientific method </available_agent_types>

<execution_context> @~/.claude/ferrox-core/workflows/debug.md </execution_context>

User's input: $ARGUMENTS

Parse subcommands and flags from $ARGUMENTS BEFORE the active-session check:

• If $ARGUMENTS starts with "list": SUBCMD=list, no further args
• If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)
• If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)
• If $ARGUMENTS contains --diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from description
• Otherwise: SUBCMD=debug, diagnose_only=false

Check for active sessions (used for non-list/status/continue flows):

ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5

Execute end-to-end.