gsd-list-phase-assumptions

Surface phase assumptions during roadmap planning by identifying technical approaches, implementation order, scope boundaries, risks, and dependencies to produce a structured summary for early course correction. This prevents misalignments before execution.

Phase assumption analysis identifies underlying expectations about technical approach, scope, and dependencies before execution begins. It is needed in planning workflows to catch conflicting assumptions early and align teams on the project roadmap.

Analyze a specific roadmap phase by validating its approach against five key areas: technical implementation, execution order, scope boundaries, risks, and dependencies. This yields actionable next steps and user feedback prompts to refine plans.

Yes, validate scope boundaries and implementation order by extracting assumptions upfront during planning sessions. This structured analysis highlights gaps and dependencies, enabling early course correction before committing to the technical approach.

The best way to catch technical approach misalignments early is to run a structured assumption analysis against the project roadmap, surfacing conflicting dependencies and scope boundaries for user feedback before implementation begins.

Avoid automated assumption analysis when your project lacks a defined roadmap or when the phase scope is entirely ambiguous, as the analysis requires a baseline technical approach and implementation order to extract meaningful risks and dependencies.