qsd-list-phase-assumptions

To surface phase assumptions before planning, you provide a phase number to analyze the roadmap, validating phase existence and identifying structured assumptions across technical approach, scope, risks, and dependencies. This prevents misalignment and scope creep before detailed execution begins.

Phase assumptions in a roadmap-driven workflow are underlying beliefs about technical approach, implementation order, scope boundaries, risks, and dependencies. Surfacing these assumptions early ensures phase-level decisions align with stakeholder expectations and improves overall planning quality.

You prevent scope creep during project planning by validating phase existence against the roadmap and documenting structured assumptions about scope boundaries. A feedback loop allows you to adjust plans and correct misaligned expectations before detailed planning or execution starts.

Yes, you can analyze roadmap dependencies and risks before planning by requesting a list of phase assumptions. The process validates the phase against the roadmap, surfaces risks and dependencies, and prompts for user feedback to guide the next steps in the workflow.

You need to review phase-level technical assumptions when early alignment on phase decisions is critical for planning quality. Applying this to roadmap-driven workflows before planning begins prevents misalignment and ensures stakeholders share a clear understanding of the technical approach.