gsd-list-phase-assumptions

To surface hidden assumptions before planning a roadmap phase, you need to extract inferred beliefs about technical approach, implementation order, scope boundaries, risks, and dependencies from your project context. This reveals potential misalignments early in pre-planning workflows.

Phase assumption discovery is the process of identifying implicit technical and scope beliefs during sprint preparation. It helps validate the roadmap by highlighting risk areas and dependency issues that could otherwise change project sequencing or boundaries.

To validate phase existence and dependencies in a project roadmap, you must check the phase identifier against available workflow documents. This grounds the analysis in project context and verifies the phase boundaries before extracting structured assumptions.

Yes, you can check technical implementation order and scope boundaries from workflow documents by providing a validated phase identifier. The system reads contextual references to extract and present structured assumptions about the phase approach.

Yes, you need read permission to contextual references for phase analysis. Access to roadmap and workflow documents is required to verify phase existence and extract structured assumptions about risks and dependencies.

You should not use assumption discovery for roadmap validation when a validated phase identifier is unavailable or when you lack access to roadmap and workflow documents, as the analysis requires these inputs to ground its findings.