gsd-list-phase-assumptions

Phase assumption review surfaces the likely technical approach, scope boundaries, risk areas, and dependencies before you create a detailed plan. It validates the requested phase number against the roadmap and grounds expectations in the current project state to prevent rework.

Phase assumptions in roadmap planning are the expected technical approach, implementation order, and scope boundaries for a development phase. You need to check them when a phase is about to be planned, ensuring the focus correctly targets refactoring, feature delivery, or migration work before investing time in a full plan.

You can identify risk areas and dependencies by requesting an assumption review for a specific phase number. This highlights likely risks and dependency expectations early, allowing your team to discuss tradeoffs and correct the implementation course before a detailed project plan is generated.

Yes, you can validate a phase number against the roadmap before planning continues. The review checks the requested phase against the roadmap and presents an assumption set grounded in the current project state and workflow context to ensure alignment.

To clarify scope boundaries and implementation order, review the phase assumptions before planning starts. This confirms whether the phase should focus on refactoring, feature delivery, or migration work, reducing rework by making technical approach and dependencies visible early enough to correct course.