investigatelisted

# Investigate Up to four research agents independently diagnose the task. You (the main agent) read the task, launch them in parallel, cross-check their findings, and report the best steps. You do NOT write any code during this skill. Works for two kinds of task: - **Fix** — a bug or broken behavior. Goal: root cause + minimal clean fix. - **Feature** — something to implement. Goal: where it goes, how to build it, and the possible approaches with trade-offs. --- ## Step 0 — Read the task and classify it Args are a task: an issue link/id, or a plain instruction. - **A task link/id was provided** → fetch its content and read title + full description (Linear via its MCP `get_issue`, GitHub issue/PR via `gh`, or fetch the URL). - **Plain instruction** → use as-is. Decide whether it's a **fix** or a **feature** (fixing broken behavior vs building something new). If unclear, default to feature framing. Restate the task in one line + the type so the user can confirm. If genuinely ambiguous, ask one focused question before spawning agents. --- ## Step 1 — Spawn research agents in parallel (2–4) Launch the agents in a single message so they run concurrently. **At most 4 at once.** Pick the count and framing by task type: - **Fix (bug)** — agents converge on the SAME goal (the one root cause). Use 2–3, each attacking it from a different angle (e.g. reproduce/trace, read suspect module, check recent changes/git blame) but all aiming at the same answer. - **Feature** — agents