protocol-d-debugging

Features and purpose

TRIGGERS: "stuck", "not working", "broken", "help", "error", "bug", "confused", "doesn't work", "can't figure out", "failing", "crashed", "won't run", "what's wrong", "why isn't this working", "I don't understand why", "it broke", "something's wrong", "can't figure this out", "I'm lost", "no idea what's happening", "unexpected behavior". USE WHEN: Junior is stuck on a bug or error and needs systematic debugging guidance. PROVIDES: Protocol D flow - READ → ISOLATE → DOCS → HYPOTHESIZE → VERIFY. PROACTIVE: Triggers when junior expresses confusion or frustration about code not working.

Quick start

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.