gsd-list-phase-assumptions

To surface project phase assumptions, you analyze the phase to identify technical approach, implementation order, scope boundaries, risk areas, and dependencies. This proactive assumption analysis prevents costly misalignments early in the development lifecycle.

Assumption analysis in project risk management is the process of identifying and validating presumed technical approaches, scope boundaries, and dependencies for a development phase. It ensures roadmap alignment and enables early course correction before resource commitment.

Validating phase planning assumptions requires reviewing the surfaced technical approach and implementation order against your project roadmap. This roadmap alignment ensures the identified scope boundaries and dependencies match the team's actual strategy.

Yes, assumption surfacing applies directly to risk assessment within a phased development lifecycle. By outlining technical challenges and required order of operations, it identifies risk areas and dependencies before detailed phase planning begins.

You need to identify scope boundaries and implementation order before committing resources to a new development phase. Performing this assumption analysis early ensures Claude's understanding of technical challenges aligns with your project strategy.

The primary limitation is that surfaced assumptions about scope and dependencies require manual validation against your project roadmap. AI-generated technical approach assumptions may contain flawed logic that needs early course correction by the team.