gsd-list-phase-assumptions

To reveal phase assumptions before planning, analyze the project phase to surface technical approach, implementation order, scope boundaries, risks, and dependencies for stakeholder alignment. This early course correction prevents roadmap misalignment.

The best way to validate a roadmap phase with stakeholders is to enumerate assumptions across five key areas: technical approach, order, scope, risks, and dependencies. Providing transparent outputs enables early alignment and course correction before planning begins.

You surface technical risks and dependencies for sprint scoping by analyzing the target phase against the project roadmap. The process enumerates hidden assumptions across technical approach and scope boundaries, concluding with a user prompt for feedback.

Yes, you can analyze project scope boundaries before committing to a plan. The skill validates the current phase description against the roadmap and transparently outputs assumptions about scope, implementation order, and dependencies to enable early course correction.

You need to analyze phase assumptions for roadmap validation because surfacing hidden assumptions about technical approach and dependencies helps teams align on strategy early. This prevents costly misalignment and scope creep during actual planning and execution.