mindforge-debuglisted

<objective> Debug issues using scientific method with subagent isolation. **Orchestrator role:** Gather symptoms, spawn mindforge-debugger agent, handle checkpoints, spawn continuations. **Why subagent:** Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction. </objective> <context> User's issue: $ARGUMENTS Check for active sessions: ```bash ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5 ``` </context> <process> ## 0. Initialize Context ```bash INIT=$(node ".agent/bin/mindforge-tools.cjs" state load) if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi ``` Extract `commit_docs` from init JSON. Resolve debugger model: ```bash debugger_model=$(node ".agent/bin/mindforge-tools.cjs" resolve-model mindforge-debugger --raw) ``` ## 1. Check Active Sessions If active sessions exist AND no $ARGUMENTS: - List sessions with status, hypothesis, next action - User picks number to resume OR describes new issue If $ARGUMENTS provided OR user describes new issue: - Continue to symptom gathering ## 2. Gather Symptoms (if new issue) Use AskUserQuestion for each: 1. **Expected behavior** - What should happen? 2. **Actual behavior** - What happens instead? 3. **Error messages** - Any errors? (paste or describe) 4. **Timeline** - When did this start? Ever worked? 5. **Reproduction** - How do you trigger it? After all gathered, confirm ready to i