Identify, analyze, and prioritize project risks using qualitative and quantitative methods. Develop mitigation strategies to minimize impact and maximize project success probability.
3f5182cRisk assessment is a systematic process of identifying potential threats to project success and developing strategies to mitigate, avoid, or accept them.
Minimal working example:
# Risk identification framework
class RiskIdentification:
RISK_CATEGORIES = {
'Technical': [
'Technology maturity',
'Integration complexity',
'Performance requirements',
'Security vulnerabilities',
'Data integrity'
],
'Resource': [
'Team skill gaps',
'Staff availability',
'Budget constraints',
'Equipment/infrastructure',
'Vendor availability'
],
'Schedule': [
'Unrealistic deadlines',
'Dependency delays',
'Scope creep',
'Approval delays',
'Resource conflicts'
],
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | Risk Identification Techniques | Risk Identification Techniques | | Risk Analysis Matrix | Risk Analysis Matrix | | Risk Response Planning | Risk Response Planning | | Risk Monitoring & Control | Risk Monitoring & Control |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/risk-assessment · pinned to the source commit
git clone https://github.com/aj-geddes/useful-ai-prompts.git
cd useful-ai-prompts
git checkout 3f5182cfd739fc113f4af5244a1cf342ad7f7911
mkdir -p ".claude/skills/risk-assessment"
cp -r "skills/risk-assessment" ".claude/skills/risk-assessment"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 3f5182cfd739. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.