gsd-list-phase-assumptions

To check project phase planning assumptions, you surface unstated beliefs about technical approach, scope boundaries, and dependencies prior to planning. This early workflow validation prevents misaligned plans and wasted effort on rework.

Unstated technical approach causes rework because incorrect assumptions about implementation order and risk areas go unchecked. Surfacing these hidden assumptions early allows you to correct misalignments before investing time in a full phase plan.

The best way to validate Claude's understanding of a project phase is to explicitly list its unstated assumptions across five key areas: technical approach, implementation order, scope boundaries, risk areas, and dependencies for early course correction.

Yes, you can use assumption checking for GSD workflow projects to align on scope boundaries. It reveals what Claude interprets as the phase requirements, ensuring dependencies and risk areas are agreed upon before detailed planning.

You surface hidden dependencies in Claude Code phase planning by applying structured assumption checking to the phase. This action explicitly lists unstated beliefs about dependencies and implementation order to enable early course correction.

You should not use assumption surfacing when a detailed execution plan is already finalized or when project phases lack defined technical approaches. It is specifically designed to validate understanding prior to creating a phase plan.