discuss-phase

You can clarify implementation decisions by analyzing phase descriptions from a roadmap to identify gray areas, guiding a focused discussion, and capturing choices in a CONTEXT.md file for downstream agents.

The best way to capture project context is by discussing phase-specific gray areas with users and documenting their decisions in a CONTEXT.md file, ensuring downstream development agents have clear scope and direction.

You manage scope boundaries by enforcing phase limits during discussions and actively deferring new capabilities or out-of-scope ideas to future phases, ensuring the current development phase maintains strict focus.

Yes, you can use roadmap phase descriptions to identify implementation gray areas by analyzing the text to pinpoint specific technical choices, such as session handling or error strategies, that require targeted user input.

You need to discuss phase-specific decisions before development begins when a roadmap phase contains ambiguous implementation choices, such as session handling or multi-device policies, that require user input to ensure downstream agents have clear context.