triagelisted

# /aiagentminder:triage - Bug Triage Systematically investigate a bug: reproduce it, diagnose the root cause, design a durable fix plan, and create a GitHub issue with the analysis. This is the structured start to debugging — complementing the debug checkpoint pattern (embedded in agent profiles) which handles the structured pause when a fix stalls. --- ## Step 1: Capture the Problem Get a clear bug description from the user (or from the skill argument). Clarify: - **Expected behavior** — what should happen? - **Actual behavior** — what happens instead? - **Steps to reproduce** — how to trigger the bug - **Error output** — error message, stack trace, or unexpected output If any of these are unclear, ask before proceeding. --- ## Step 2: Explore and Diagnose Use the Agent tool to spawn an exploration subagent (`subagent_type: "Explore"`). The subagent's job: 1. Trace the code path from the entry point (the user action or API call that triggers the bug) to the failure point. 2. Read relevant source files, tests, and configuration — not the entire codebase. 3. Report back: - The code path involved - Where the failure occurs - A root cause hypothesis **Durability principle:** Describe the root cause in terms of behaviors and contracts, not line numbers or internal variable names. The diagnosis should remain useful even if the code is refactored. --- ## Step 3: Validate Root Cause Attempt to confirm the root cause hypothesis: - Run relevant tests to see if