⚡ EXECUTION INSTRUCTIONS FOR CLAUDE

When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.

🚨 EXECUTION WORKFLOW

Phase 1: Execute Documented Workflow

Action Steps:

1. Review the reference documentation below and execute the detailed steps sequentially.

📋 REFERENCE DOCUMENTATION

debugp - Alias for Debug Protocol

Usage: /debugp [issue description] Alias for: /debug-protocol

This command is a shorthand alias for the comprehensive Debug Protocol command.

For full documentation and usage, see: debug-protocol.md

Quick Reference

Apply comprehensive forensic debugging methodology for complex issues requiring systematic evidence gathering, hypothesis validation, and documented root cause analysis.

🚨 TOTAL FAILURE PROTOCOL: Enforces Total Failure Protocol - 100% issue resolution or TOTAL FAILURE.

Use /debugp (or /debug-protocol) for:

• Complex production issues requiring forensic analysis
• Critical bugs where thoroughness is essential
• Issues requiring evidence documentation
• Team debugging scenarios needing clear methodology
• High-stakes debugging where validation is critical

Use /debug for:

• Routine debugging and quick issues
• General debugging with other commands (/debug /test)
• Lightweight debugging scenarios