Stats
Actions
Tags
From maestro
Executes Maestro debugging workflow for investigation-heavy tasks: reproduce failures, form hypotheses, gather evidence from code/logs/tests/runtime, isolate root causes, verify fixes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/maestro:debugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read `${CLAUDE_PLUGIN_ROOT}/references/architecture.md`.
Read ${CLAUDE_PLUGIN_ROOT}/references/architecture.md.
Before delegating, activate the delegation skill to ensure agent-base-protocol and filesystem-safety-protocol are injected into the delegation prompt.
npx claudepluginhub josstei/maestro-orchestrate --plugin maestroDiagnoses failures, fixes bugs, and investigates failing tests using systematic debugging: reproduce first, read before changing, assume nothing, find root cause.
Runs parallel AI agent investigations on a bug/issue and produces a consolidated debug report. Use for debugging, error analysis, or problem diagnosis.
Provides systematic debugging framework for root cause analysis after 2+ failed fixes, complex failures, intermittent bugs, and circular debugging.