gsd-discuss-phase

To gather phase context for research planning, load prior context files like PROJECT.md, REQUIREMENTS.md, and STATE.md to establish the current decision landscape. This process identifies undecided areas for discussion and produces a phase-specific CONTEXT.md to guide downstream agents.

Tracking phase decisions and surfacing gray areas involves scanning the codebase for reusable assets and loading prior context files. Presenting these gray areas for user selection locks decisions and generates a concrete phase-specific CONTEXT.md that downstream agents can act on without asking again.

Generate a phase-specific CONTEXT.md by running the discuss workflow with a phase number. This loads prior context, scouts for reusable project artifacts, and locks user decisions into a concrete {phase_num}-CONTEXT.md file that downstream agents can act on independently.

Yes, you can skip interactive questions during pre-planning by passing the --auto flag. This bypasses adaptive questioning and automatically applies recommended defaults to generate the phase-specific CONTEXT.md without user intervention.

Context management for research planning requires existing project files to establish the decision landscape. The process loads PROJECT.md, REQUIREMENTS.md, STATE.md, and any prior CONTEXT.md files to identify gray areas and lock phase decisions effectively.

Downstream agents ask for phase decisions during execution when a phase-specific CONTEXT.md is missing or lacks clear decisions. Establishing context through adaptive pre-planning locks these decisions upfront, ensuring downstream agents can act without asking the user again.