// Use when debugging issues that involve external services, database state, or API behavior — complements superpowers:systematic-debugging with MCP tool usage
Use when querying, modifying, or investigating database state — enforces schema-first approach and mutation safety
Use when implementing features that use external libraries or APIs — ensures docs-first approach before writing code
Use when investigating libraries, APIs, or unfamiliar patterns before implementation — guides doc lookup and web search workflow
| name | mcp-debugging |
| description | Use when debugging issues that involve external services, database state, or API behavior — complements superpowers:systematic-debugging with MCP tool usage |
Use this workflow when debugging issues that may involve external services, database state, or API behavior. This complements superpowers' systematic-debugging skill — use that first for root cause analysis methodology, then use this skill for MCP-specific investigation tools.
If superpowers:systematic-debugging applies, invoke it first. This skill adds MCP-specific investigation techniques on top of that methodology.
Use available Gateway tools to collect evidence:
Collect first, hypothesize second.
Based on evidence from Step 1:
| If the issue is in... | Investigation approach |
|---|---|
| Database | Schema check → query affected tables → trace data flow |
| External API | Check docs for changes → test with minimal request → verify auth |
| Application logs | Filter for error patterns → trace request flow → check timestamps |
| Unknown | Search web for the specific error message |
After implementing a fix:
