gsd:workflow:list-phase-assumptions

To document phase assumptions for project management workflows, you can run the gsd:workflow:list-phase-assumptions skill, which systematically identifies and organizes phase-specific details into a structured format. It requires phase-specific details as input to generate the comprehensive assumption list.

Phase assumption management is the process of identifying and documenting underlying workflow expectations to proactively address potential blockers. It is needed for risk mitigation because it highlights critical dependencies early, ensuring that project risks are appropriately accounted for and mitigated.

To highlight dependencies and mitigate risks in a software development project, this Skill analyzes your provided phase-specific details and maps out critical dependencies for each documented assumption. This structured approach ensures that all project risks are accounted for and mitigated.

Yes, you can use this Skill to manage and review phase assumptions in workflows because it actively supports Bash, Glob, Grep, and Write tools. This implementation allows you to automate the identification, documentation, and organization of assumptions via scripts.

The best way to structure dependency management for project phases is to use a Skill that generates a comprehensive list of phase assumptions from your specific inputs. This approach provides a structured framework to highlight critical dependencies and plan risk mitigation strategies effectively.