gsd-discuss-phase

Surfacing assumptions involves guiding adaptive questioning across product, engineering, and design contexts, asking clarifying questions one at a time to resolve ambiguities before planning begins.

Locking decisions requires writing entries to a CONTEXT.md file, ensuring decisions remain immutable after locking. This gated approach prevents scope creep by blocking phase progression until all gray areas have locked decisions.

A phase-gate process works by enforcing a strict decision gate that blocks progression until all identified gray areas have locked decisions, requiring one-at-a-time clarifications to resolve ambiguities before moving forward.

Yes, clarifying phase context requires reading phase goals from .planning/ROADMAP.md and relevant requirements from .planning/REQUIREMENTS.md to understand the scope before asking adaptive questions.

Use a strict decision lock when planning phases have ambiguity across product, engineering, and design contexts. It enforces a gated CONTEXT.md file and provides a clear exit condition only after all gray areas are resolved.