gsd-list-phase-assumptions

To identify implicit assumptions in a project roadmap, you extract phase descriptions and technology constraints from the roadmap content. This process surfaces hidden architecture and scope assumptions, producing a structured list to verify planning alignment.

Validating phase assumptions involves inspecting specific roadmap phases to generate a concise, checkable summary of architecture hints and technology constraints. This structured output guides planning discussions and reduces misalignment across the project.

You extract technology constraints and architecture hints by analyzing the roadmap content for a specified phase. The process identifies implicit assumptions and outputs a structured, checkable summary to guide technical planning and scope verification.

Yes, you can check a specific roadmap phase for hidden planning risks by specifying the phase number. The analysis identifies implicit assumptions regarding architecture and technology choices, outputting a list to mitigate scope misalignment before planning.

Yes, you need existing roadmap content and defined phase descriptions to list phase assumptions. The process requires access to this roadmap data to extract implicit architecture and technology constraints for generating a structured planning summary.