gpd-list-phase-assumptions

To extract phase assumptions from a roadmap, analyze roadmap descriptions to identify physical, mathematical, computational, and scope assumptions. This surfaces underlying premises to inform planning decisions and guide risk mitigation discussions.

Physical and computational assumptions in phase planning are the underlying premises extracted from roadmap descriptions regarding system constraints and resource availability. Identifying these assumptions helps flag high-risk areas for early validation before execution.

Yes, you need ROADMAP.md and STATE.md files in the project state to validate phase existence. The skill requires access to these files to accurately analyze descriptions and produce a structured YAML report for planning.

Yes, you can generate a structured risk analysis report by analyzing roadmap descriptions to flag high-risk or weakly supported assumptions. This produces a structured YAML report suitable for guiding planning steps and risk mitigation.

The best way to surface AI assumptions for roadmap phase planning is to run an analysis on specified phases to extract scope and computational premises. This approach flags weakly supported assumptions early to validate phase existence and guide discussions.

You should validate weakly supported assumptions before phase planning to mitigate risks early. Flagging high-risk assumptions extracted from roadmap descriptions prevents planning errors and ensures computational and scope premises are actively reviewed.