gsd-list-phase-assumptions

To surface phase assumptions, prompt Claude to identify and present its assumptions about technical approach, implementation order, scope, risks, and dependencies before you draft the full plan. It validates the phase number against the roadmap to ensure alignment.

The best way to align teams is presenting Claude's phase assumptions upfront for early feedback. Exposing implementation order, scope boundaries, and dependencies facilitates course correction before committing to a drafted plan.

You validate the phase number by requesting a phase assumption review. The process checks the input phase against the existing roadmap to confirm existence, then outputs assumptions and recommended next steps for that specific phase.

You need to identify phase assumptions during roadmap reviews and phase analysis, specifically before planning begins. This exposes technical approach, implementation order, scope boundaries, risks, and dependencies to avoid missteps.

Yes, surfacing roadmap assumptions works without predefined dependencies because the Skill operates independently to identify risks and dependencies. It actively reveals these factors during the phase analysis to guide your next steps.