gsd:workflow:list-phase-assumptions

To document phase assumptions for a project workflow, you capture and review project dependencies, risks, and planning details to create a structured, auditable record that guides decision-making.

The best way to track project phase dependencies and risks is to document them in structured notes that highlight potential issues, enabling proactive mitigation and preventing scope creep.

You need to validate project phase assumptions during workflow planning to prevent misalignment, ensuring that dependencies and risks are reviewed before moving forward.

Documenting assumptions helps with project risk management by highlighting dependencies and potential risks, which enables proactive mitigation and creates an auditable record for future planning.

Yes, you can use this workflow for multiple project phases. It applies to reviewing dependencies, risks, and future planning across the entire project lifecycle to maintain alignment.

You should capture assumptions because it creates a structured, auditable record that prevents scope creep and misalignment, while mapping dependencies and risks for proactive mitigation.