gsd-cc-discuss

To clarify ambiguous requirements before planning, identify gray areas across state, planning, data, and tools, then document each decision with rationale in a CONTEXT.md file. This ensures a formal record of decisions to guide the next planning steps.

A decision record captures implementation choices, constraints, and rationale during pre-planning. You need one when a route or slice has unclear requirements, ensuring a formal traceable record of decisions is written to CONTEXT.md before planning proceeds.

You document implementation decisions and rationale by loading context from state files and writing a CONTEXT.md file. This captures the debate and concrete decisions, providing traceability for stakeholders during the planning process.

Yes, capturing stakeholder context helps surface ambiguities by loading context from state files to identify gray areas in the current slice. This ensures implementation decisions and constraints are recorded with rationale in CONTEXT.md.

The best way to generate a CONTEXT.md file is to run a pre-planning discussion that identifies gray areas across state, planning, data, and tools, then writes concrete decisions with rationale to the file for the current slice.