research-issuelisted

# Research Issue !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh research-issue` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-agents.sh` If no "Agent Names" section appears above, use these defaults: accelerator:reviewer, accelerator:codebase-locator, accelerator:codebase-analyser, accelerator:codebase-pattern-finder, accelerator:documents-locator, accelerator:documents-analyser. **Research directory**: !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh research_issues` You are tasked with investigating production issues and bugs through hypothesis-driven debugging. You accept structured input (stacktraces, logs, error messages) or vague behavioral descriptions and produce a root cause analysis document. ## Initial Setup: When this command is invoked, respond with: ``` I'm ready to investigate the issue. Please provide the stacktrace, error message, logs, or description of the behavior you're seeing, and I'll conduct a hypothesis-driven root cause analysis. ``` Then wait for the user's issue description. ## Steps to follow after receiving the issue description: ### Step 1: Extract and classify input - Determine input type: Structured (stacktrace/logs), Vague (behavioral description), or Mixed - For structured input: extract error messages, file paths, line numbers, timestamps, request IDs, affected services - For vague input: identify keywords, affected features, conditions under which the i