gsd-discuss-phase

Gather project context by loading prior files like PROJECT.md and STATE.md to avoid re-asking decided questions. This process interactively surfaces gray areas and unresolved decisions, producing a CONTEXT.md artifact to prevent downstream clarification requests.

Consolidate phase decisions by running a guided discussion that scouts the codebase for gray areas. This produces a phase-specific CONTEXT.md decision artifact that locks down integration choices and serves as a single source of truth for downstream automation.

Generate CONTEXT.md automatically by using auto mode, which applies recommended defaults for unresolved decisions instead of interactively narrowing topics. This still loads existing workflow context and outputs the required decision artifact for researchers.

Yes, this context-gathering workflow requires existing files like PROJECT.md, REQUIREMENTS.md, and STATE.md. It loads these templates to consolidate prior context and avoid re-asking questions that have already been decided.

Run an interactive discussion phase at the start of an implementation phase to clarify ambiguous requirements. This ensures integration choices and context gaps are resolved before planning, allowing downstream researchers to proceed without interruption.