gsd-list-phase-assumptions

To surface project assumptions, analyze roadmap phases to identify implicit technical strategy, scope, and risks before planning begins. This prevents misalignment by forcing explicit validation of implementation order and dependencies early.

Assumption surfacing in project workflows is the process of identifying implicit technical approaches, scope boundaries, and dependencies within roadmap phases. It provides transparency into reasoning to enable early course correction.

You need to list phase assumptions before starting complex tasks like a major refactor, ensuring the agent understands risk areas and technical constraints. This prevents investing time in detailed planning based on misunderstandings.

Yes, you can validate technical strategy by analyzing project state files and roadmap documentation. This generates phase-specific insights into implementation order, scope boundaries, and risk assessment.

The best way to prevent misalignment is forcing the explicit statement of underlying assumptions regarding technical strategy and risk before any phase execution begins. This allows early course correction of misunderstandings.

Yes, you need access to roadmap documentation and project state files to generate accurate, phase-specific risk assessments. This documentation provides the context required for transparent assumption surfacing.