dan:discuss

To capture project decisions and constraints, run a structured discuss phase to surface tradeoffs and generate a CONTEXT.md file. This process identifies 3-7 key gray areas where multiple valid approaches exist and documents them for downstream planning and execution.

A structured discuss phase in product planning is a focused interview process that surfaces decisions, tradeoffs, and success criteria. It identifies key gray areas and produces a phase CONTEXT.md to ensure team alignment before research and execution begin.

You generate a CONTEXT.md file by initiating a discuss phase for a specific phase number. The process parses the target phase, loads prior context, conducts interactive questioning on gray areas, and writes the output to .planning/phases/{phase-dir}/{phase}-CONTEXT.md.

Yes, you can avoid re-arguing settled decisions by loading prior context during the discuss phase. This cross-phase continuity ensures previous decisions and constraints are carried forward, maintaining alignment and preventing duplicate discussions.

Yes, this approach works for identifying gray areas in requirements gathering by systematically discovering 3-7 key decision points. It conducts focused questioning to surface multiple valid approaches, deferred ideas, and open questions for product teams.

The discuss phase for stakeholder alignment focuses on early-stage projects and produces a CONTEXT.md capturing decisions and open questions. It is limited to identifying gray areas and does not execute the project itself, serving strictly as a preparatory planning step.