debug-wplisted

# Skill: debug-wp ## When to Use Use this skill when diagnosing any WordPress problem - white screen of death, plugin conflicts, 500 errors, broken layouts, admin lockouts, performance issues, migration failures, cron problems, or any "it was working yesterday" scenario. Do NOT jump to solutions. Always complete the triage interview first. Use `$ARGUMENTS` as the initial symptom description. If empty, ask the user to describe the issue. ## Procedure ### Phase 1: Triage Interview Ask questions in this order. Use `AskUserQuestion` where possible for structured input. Stop early if the user provides enough context to confidently diagnose (including any symptom passed via `$ARGUMENTS`). #### 1. Symptom - What exactly is broken? (white screen, error message, wrong content, slow load, redirect loop, etc.) - Is there a specific error message or error code? (copy/paste the exact text) - Does it affect the frontend, the admin (`/wp-admin`), or both? #### 2. Trigger - When did this start? (after an update, migration, hosting change, new plugin, code edit) - What was the last change made before the issue appeared? - Was anything recently updated? (WordPress core, theme, plugin, PHP version, server config) #### 3. Scope - Does it affect all pages or specific pages/post types? - Does it affect all users or only logged-in / logged-out users? - Does it affect all browsers / devices or specific ones? - Is this a single site or WordPress Multisite? #### 4. Environment - WordPre