mindforge-research-phaselisted

<objective> Research how to implement a phase. Spawns mindforge-phase-researcher agent with phase context. **Note:** This is a standalone research command. For most workflows, use `/mindforge-plan-phase` which integrates research automatically. **Use this command when:** - You want to research without planning yet - You want to re-research after planning is complete - You need to investigate before deciding if a phase is feasible **Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results. **Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction. </objective> <context> Phase number: $ARGUMENTS (required) Normalize phase input in step 1 before any directory lookups. </context> <process> ## 0. Initialize Context ```bash INIT=$(node ".agent/bin/mindforge-tools.cjs" init phase-op "$ARGUMENTS") if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi ``` Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`, `state_path`, `requirements_path`, `context_path`, `research_path`. Resolve researcher model: ```bash RESEARCHER_MODEL=$(node ".agent/bin/mindforge-tools.cjs" resolve-model mindforge-phase-researcher --raw) ``` ## 1. Validate Phase ```bash PHASE_INFO=$(node ".agent/bin/mindforge-tools.cjs" road