gsd-list-phase-assumptions

To surface phase assumptions before project planning, provide a phase number and roadmap context to trigger an analysis of technical scope, risks, and dependencies. This generates structured assumptions and prompts for user feedback to align teams early.

Phase assumption analysis in roadmap-based projects is the process of identifying assumed technical approaches, scope boundaries, and dependencies before planning begins. It helps teams correct misalignment early by generating structured prompts for feedback.

You can identify dependency mapping and risk-assessment gaps by supplying roadmap and phase descriptions to generate structured assumptions. This process highlights missing scope elements, ordering issues, and risks to inform downstream planning.

Yes, phase planning assumptions apply directly to multi-phase roadmap analysis. The process requires access to project roadmaps and phase descriptions to identify scope gaps, dependencies, and risks across all defined phases.

The best way to align teams on technical approach before phase planning is to surface structured phase assumptions and generate targeted prompts for user feedback. This quick corrective action resolves misalignment on scope, risks, and dependencies early.

You need to map out phase-level assumptions for a project roadmap when early alignment on technical approach, scope, risks, and dependencies is required. This is essential for roadmap-based projects spanning multiple phases before planning begins.