gsd-list-phase-assumptions

To surface phase assumptions before planning, provide a phase number to validate its existence against the roadmap and summarize technical approach, sequencing, scope boundaries, risks, and dependencies. This prevents misalignment and rework by revealing Claude's assumptions upfront.

Analyzing phase risks and dependencies involves validating the phase against the roadmap and summarizing technical approach, scope boundaries, and sequencing. This structured approach outputs a concise assumption set with a prompt for user feedback to align stakeholders.

Validating a project phase against the roadmap requires providing the phase number to enforce that the phase exists. The process checks the roadmap and outputs a concise assumption set covering technical approach, risks, and dependencies for stakeholder review.

Yes, you can get a structured feedback loop for phase planning assumptions by prompting 'What do you think?' after generating a concise assumption set. This enables quick feedback loops to align stakeholders on technical approach, scope, and risks.

No, phase assumption analysis requires existing roadmap documentation because it validates the selected phase against the roadmap. It enforces that the phase exists and analyzes phase descriptions to surface technical approach and dependencies.

Before starting technical implementation, check scope boundaries by summarizing the assumptions Claude makes about the selected phase. This includes analyzing phase descriptions to surface implementation order, risks, and dependencies against the roadmap.