mh-cto-sdlc-risk-register

To create a risk register during the SDLC analysis phase, the Skill automatically identifies, assesses, and prioritizes project risks by likelihood and severity, then generates a detailed document with mitigation strategies.

The best way to prioritize project risks by likelihood and severity is using a scoring matrix that multiplies both factors to calculate criticality levels, enabling strategic mitigation planning for high-priority threats.

You can generate mitigation strategies for identified project risks by categorizing them into market, technical, execution, or assumption groups, then defining specific triggers, actions, and contingency plans for each.

Yes, you can use this risk register tool for project planning without external dependencies. It operates independently using scripts and references, but requires access to project context and Phase 1 analysis artifacts.

You need to update a project risk register whenever new project context or Phase 1 analysis artifacts become available. Maintaining the register ensures risk scores and mitigation strategies remain aligned with current project realities.

No, the risk register handles technical and execution risks using the same mechanism. Both are classified by category, scored on severity and likelihood, and assigned matching triggers, actions, and contingency plans for mitigation.