gsd-list-phase-assumptions

To surface phase assumptions, you validate the phase number against your roadmap and generate a comprehensive assumption list covering technical approach, implementation order, scope boundaries, risks, and dependencies before any planning begins.

Assumption-first phase planning is the process of listing an agent's assumptions about a phase's technical approach, scope, risks, and dependencies before planning starts. You need it to prevent building a misaligned roadmap execution plan.

Validating a phase number requires checking the requested phase against the project's roadmap to ensure the phase exists, then mapping assumptions across the technical approach, implementation order, scope boundaries, risks, and dependencies.

Yes, you can map technical approach and dependency assumptions by providing the phase number as an argument, which triggers a roadmap existence check and outputs assumption coverage across implementation order, scope boundaries, and risk assessment.

Planning a phase without validating assumptions risks building the wrong plan due to misaligned technical approaches, incorrect implementation order, undefined scope boundaries, unmapped dependencies, and unidentified risks.

The best way to prevent misaligned planning is to conduct an assumption-first phase review that validates the phase number, maps dependencies and risks, and prompts for user feedback with a 'What do you think?' question before generating any plan.