gsd-discuss-phase

Decision capture during a structured discuss phase locks unresolved implementation choices into a phase-numbered CONTEXT.md file. This prevents downstream researchers and planners from guessing or repeatedly asking the user for clarification.

Adaptive questioning identifies remaining gray areas and unresolved decisions during codebase scouting. It dynamically routes behavior based on discuss mode and assumptions flags to ensure all planning alignments are addressed before execution.

Run the discuss phase workflow with a required phase number argument to produce a phase-specific CONTEXT.md file. This file captures concrete decisions, locks choices, and clarifies next investigations for downstream agents.

Yes, routing for assumptions versus discussion supports a fast path for assumption review and a separate guided path for interactive discussion. The workflow routes behavior dynamically based on assumptions flags and discuss mode settings.

Yes, loading prior context is required before running the discuss workflow. The adaptive process must load existing context to identify gray areas, surface remaining decisions, and build planning alignment effectively.

Planning alignment is achieved by running a selection-driven deep dive across research phases. This captures unresolved decisions and implementation choices into a phase-numbered CONTEXT.md, ensuring downstream agents can act without re-asking.