npx claudepluginhub lvlup-sw/exarchos# Debug Start debug workflow for: "$ARGUMENTS" ## Workflow Overview Debug workflows are **investigation-first**: understand the problem before fixing it. **Single human checkpoint:** Merge confirmation (after fix is validated). ## Skill Reference Follow the debug skill: `@skills/debug/SKILL.md` ## Command Variants ### Default: Thorough Track Full investigation with RCA documentation. ### Fast Path: Hotfix Track Time-boxed investigation (15 min), minimal ceremony. ### Escalate: Feature Workflow Handoff Hands off to `/exarchos:ideate` with preserved context. ### Mid-Work...
/debugDiagnoses Claude Office add-in deployment issues like stale configs, connection failures, missing add-ins, and auth errors via admin triage playbook.
/debugRuns autonomous bug-hunting loop with scientific method and autoresearch iterations to find all bugs. Supports --fix, --scope, --symptom, --severity, --iterations flags.
/debugInvokes oac:debugger skill to diagnose bugs, test failures, or unexpected behavior exactly as specified, before any fix proposals.
/debugSystematically debugs code issues via reproduce-isolate-analyze-hypothesize-test-fix process, delivering step-by-step plans, root causes, fixes, prevention, and regression tests.
/debugOrchestrates four specialist agents to systematically debug a code task description, producing problem analysis, refined hypotheses, diagnostic plan, and user confirmation request.
/debugInvokes debug-like-expert skill to systematically debug the specified issue via evidence gathering, hypothesis testing, and verification.
Start debug workflow for: "$ARGUMENTS"
Debug workflows are investigation-first: understand the problem before fixing it.
/exarchos:debug → Triage → Investigate → [Fix] → Validate → [CONFIRM] → merge
│
┌─────────────┼─────────────┐
│ │ │
--hotfix (default) --escalate
│ │ │
Fast path Thorough path → /exarchos:ideate
(15 min) (full RCA)
Single human checkpoint: Merge confirmation (after fix is validated).
Follow the debug skill: @skills/debug/SKILL.md
/exarchos:debug "Users report cart total is wrong after removing items"
Full investigation with RCA documentation.
/exarchos:debug --hotfix "Production login is returning 500 errors"
Time-boxed investigation (15 min), minimal ceremony.
/exarchos:debug --escalate "This requires redesigning the auth system"
Hands off to /exarchos:ideate with preserved context.
/exarchos:debug --switch-thorough
Switch from hotfix to thorough track during investigation.
Initialize workflow state using mcp__plugin_exarchos_exarchos__exarchos_workflow with action: "init":
featureId to debug-<issue-slug>workflowType to "debug"Then update the track using mcp__plugin_exarchos_exarchos__exarchos_workflow with action: "set":
track to "hotfix" or "thorough" based on triageGather context using @skills/debug/references/triage-questions.md:
Select track based on urgency and complexity.
Hotfix Track:
Thorough Track:
| Argument | Effect |
|---|---|
<description> | Bug description for triage context |
--hotfix | Select hotfix track (P0 urgency) |
--escalate | Hand off to /exarchos:ideate workflow |
--switch-thorough | Switch from hotfix to thorough mid-workflow |
Debug workflows use extended state schema. See @skills/debug/references/state-schema.md.
Key fields:
workflowType: "debug"track: "hotfix" | "thorough"urgency: { level, justification }triage: { symptom, reproduction, affectedArea, impact }investigation: { rootCause, findings }Debug workflows auto-chain through phases with ONE human checkpoint.
Both tracks:
[all phases auto-chain] → merge confirmation (HUMAN)
Debug workflows resume via MCP auto-discovery:
/exarchos:rehydrate
| Signal | Use /exarchos:debug | Use /exarchos:refactor |
|---|---|---|
| Something is broken or wrong | Yes | No |
| Code works but is messy/complex | No | Yes |
| Users report a bug or regression | Yes | No |
| Performance degradation | Start with /exarchos:debug (investigate) | Escalate to /exarchos:refactor if structural |
| "This should be reorganized" | No | Yes |
| Error in production logs | Yes | No |
Rule of thumb: If there is a symptom (something that should work but doesn't), use /exarchos:debug. If there is dissatisfaction with working code (hard to read, violates SOLID, duplicated logic), use /exarchos:refactor.
@skills/debug/references/rca-template.md@skills/debug/references/triage-questions.md@skills/debug/references/investigation-checklist.md@skills/debug/references/state-schema.md