gsd-list-phase-assumptions

Phase planning requires validating the phase against the roadmap to surface structured assumptions for technical approach, implementation order, scope boundaries, risk areas, and dependencies. This prevents misalignment and rework before initiating project planning.

Dependency mapping for phase validation identifies and structures the dependencies and risk areas associated with a specific project phase. It produces a ready-to-review output that validates the phase against the overall roadmap before planning begins.

To identify scope boundaries and risk areas for a project phase, validate the phase against the roadmap to generate structured assumptions. This covers technical approach, implementation order, and dependencies to prompt user feedback with a clear next step.

Validating a roadmap phase requires surfacing structured assumptions for the technical approach, implementation order, scope boundaries, risk areas, and dependencies. Providing the phase number produces a ready-to-review output that prompts user feedback.

The best way to prevent misalignment and rework during phase planning is to surface structured assumptions across multiple dimensions before initiating the project. Validating the phase against the roadmap produces a structured output for review.