gsd-list-phase-assumptions

To surface planning assumptions, you validate the phase against the roadmap and analyze its technical approach, implementation order, scope boundaries, risks, and dependencies. This prevents misalignment by prompting user feedback before the actual plan is drafted.

The core dimensions to analyze for phase dependencies and risks include the technical approach, implementation order, scope boundaries, risk areas, and dependencies. Surfacing assumptions across these five areas ensures alignment before planning begins.

You validate a phase against the roadmap by checking its existence and alignment within the workload context. This ensures the phase is recognized in the roadmap before analyzing its technical assumptions and prompting for user feedback.

You should review phase-level assumptions during phase kickoffs, roadmap reviews, and planning retrospectives. Surfacing hidden assumptions about scope boundaries and dependencies at these points prevents wasted effort and misalignment.

Yes, you can use this approach to refine technical scope boundaries. It presents assumptions about scope and implementation order, then prompts for user feedback to decide next steps before you commit to drafting a plan.

The best way to prevent misalignment in roadmap-driven phase planning is to surface assumptions about technical approach, implementation order, scope, risks, and dependencies early. Validating the phase against the roadmap and prompting feedback ensures alignment.