mindforge-discuss-phaselisted

<objective> Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked. **How it works:** 1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files) 2. Scout codebase for reusable assets and patterns 3. Analyze phase — skip gray areas already decided in prior phases 4. Present remaining gray areas — user selects which to discuss 5. Deep-dive each selected area until satisfied 6. Create CONTEXT.md with decisions that guide research and planning **Output:** `{phase_num}-CONTEXT.md` — decisions clear enough that downstream agents can act without asking the user again </objective> <execution_context> @.agent/workflows/mindforge-discuss-phase.md @.agent/workflows/mindforge-discuss-phase-assumptions.md @.agent/templates/context.md </execution_context> <context> Phase number: $ARGUMENTS (required) Context files are resolved in-workflow using `init phase-op` and roadmap/state tool calls. </context> <process> **Mode routing:** ```bash DISCUSS_MODE=$(node ".agent/bin/mindforge-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ``` If `DISCUSS_MODE` is `"assumptions"`: Read and execute @.agent/workflows/mindforge-discuss-phase-assumptions.md end-to-end. If `DISCUSS_MODE` is `"discuss"` (or unset, or any other value): Read and execute @.agent/workflows/mindforge-discuss-phase.md end-to-end. **MANDATORY:** The execution_context