debuglisted

# Debug Diagnose and fix the error, failing test, or unexpected behavior the user described. ## 1. Gather context Ask for (or extract from what the user provided): - The **error message or stack trace** (exact text preferred) - The **file(s)** involved, if known - How to **reproduce** the problem (command, test name, steps) - Whether the error is **new** (regression) or has existed for a while If the user has already provided all of this, skip asking and proceed. ## 2. Confirm the working branch Run `git branch --show-current`. If the branch is `main` or `master`, warn the user and ask whether to create a fix branch before making changes. Do not create or switch branches automatically — just ask. ## 3. Read before acting Before routing to an engineer: - Read the files mentioned in the error or stack trace. - If a test is failing, read the test file and the code it exercises. - Check `memory/**/*.md` (if the directory exists) for any known-issues entries that match the symptom. - Form a hypothesis about the root cause. State it explicitly. ## 4. Route to the appropriate engineer If the error is localized to one layer, select based on file type: | File type | Engineer | |-----------|----------| | `.cs` / .NET | **csharp-engineer** | | `.ts` / `.vue` | **frontend-engineer** | | `.ts` in an MCP server | **mcp-engineer** | | SQL / migration | **database-engineer** | **Multi-layer errors:** If the error spans layers (e.g., a frontend test failing because a backend API i