gsd-discuss-phase

Capture phase context by loading prior files like PROJECT.md, REQUIREMENTS.md, and STATE.md, then scout the repository to produce a CONTEXT.md that resolves uncertainties and guides downstream research actions.

Standardize phase context decisions by applying adaptive questioning to resolve uncertainties across requirements, state, and roadmap analyses, producing a deterministic plan that prevents rework and repeated questions.

Yes, the discuss-phase workflow requires access to PROJECT.md, REQUIREMENTS.md, and STATE.md files along with the repository workspace to load prior context and scout for reusable assets before generating decisions.

Yes, adaptive questioning enables interactive deep-dives specifically where needed, capturing decisions and rationale in a formal context document to prevent downstream agents from re-asking already resolved questions.

Context documentation guides downstream research agents by creating a deterministic plan from resolved uncertainties, outputting decisions and next steps that direct their actions without re-asking previously resolved questions.

Avoid automated context generation when prior context files like PROJECT.md or STATE.md are missing, or when the repository workspace is inaccessible, as the workflow depends on loading these assets to resolve uncertainties.