gsd-discuss-phase

Gather phase context through adaptive questioning before planning to prevent repeating decisions and surface gray areas. It anchors discussions by loading prior context, generating a structured CONTEXT.md to guide downstream researchers and planners.

Generate CONTEXT.md by triggering an adaptive discussion with your phase number. The process loads prior context, identifies gray areas, deep-dives into selected uncertainties, and writes a structured CONTEXT.md file to guide downstream execution agents.

Yes, phase context gathering loads prior context including PROJECT.md, REQUIREMENTS.md, STATE.md, and prior CONTEXT.md files. It uses these existing documents to anchor discussions, enforce phase boundary validation, and identify gray areas for deep-diving.

Identify gray areas by applying adaptive questioning that loads prior context and enforces phase boundary validation. This surfaces deferred decisions and uncertainties, capturing them in a structured CONTEXT.md to guide downstream researchers and planners.

After deep-diving into selected gray areas, propose next steps and capture deferred ideas for later phases within the generated CONTEXT.md. This ensures downstream agents receive structured guidance while documenting deferred items for future execution.

Avoid adaptive context gathering when no prior decisions or context files exist, as it requires PROJECT.md, REQUIREMENTS.md, or STATE.md to anchor discussions. It suits planning workflows where prior decisions exist and gray areas remain unresolved.