investigatelisted

Investigate the following topic: $ARGUMENTS Current repo state: !`git status --short | head -20` ## Pre-computed Context Available user skills: !`( ls -1 ~/.claude/skills 2>/dev/null ; ls -1 .claude/skills 2>/dev/null ) | sort -u | grep . | tr "\n" "," | sed "s/,$//" | grep . || echo "(none)"` Available MCP servers: !`( jq -r '.mcpServers // {} | keys[]' .mcp.json 2>/dev/null ; jq -r '.mcpServers // {} | keys[]' ~/.claude.json 2>/dev/null ) | sort -u | grep . | tr "\n" "," | sed "s/,$//" | grep . || echo "(none)"` ## Instructions 1. Parse `$ARGUMENTS` for `(ticket-dir: <path>)` to determine the output destination so downstream `/scout` and `/plan2doc` find the artifact at its canonical path: - If `ticket-dir` is specified: route findings to `{ticket-dir}/investigation.md`. - If `ticket-dir` is not specified: search `.simple-workflow/backlog/product_backlog/` and `.simple-workflow/backlog/active/` using Glob for directories matching `$ARGUMENTS` keywords. If a match is found in `product_backlog`, move it to `active` with `mv .simple-workflow/backlog/product_backlog/{ticket-dir} .simple-workflow/backlog/active/{ticket-dir}` and use `.simple-workflow/backlog/active/{ticket-dir}` as the ticket-dir. If already in `active`, use it as-is. - If no ticket-dir and no matching ticket: use the default `.simple-workflow/docs/research/` directory. 2. Investigate the topic thoroughly via the spawned researcher subagent (no direct Read/Grep loops at the orchestrator level — re