About risk-assessment
A project-planning skill for identifying, prioritizing, and responding to risks. It provides guidance for teams assessing uncertainty throughout a project, from planning through ongoing monitoring.
Key features
- 01Risk identification categories
- 02Risk analysis matrix guidance
- 03Risk response planning
- 04Risk monitoring and control practices
- 05Risk register review recommendations
Use cases
- 01Assessing risks during project planning
- 02Reviewing risks before major decisions
- 03Evaluating new technology or third-party integrations
- 04Tracking budget, schedule, or compliance risks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ aj-geddes/ useful-ai-prompts --skill risk-assessmentAfter installing, type/risk-assessmentin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/risk-analysis-matrix.mdrisk-identification-techniques.mdrisk-monitoring-control.mdrisk-response-planning.mdtemplates/process-template.mdDetails
From the project READMERisk Assessment
Table of Contents
Overview
Risk assessment is a systematic process of identifying potential threats to project success and developing strategies to mitigate, avoid, or accept them.
When to Use
- Project initiation and planning phases
- Before major milestones or decisions
- When introducing new technologies
- Third-party dependencies or integration
- Organizational or resource changes
- Budget or timeline constraints
- Regulatory or compliance concerns
Quick Start
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)
Reference Guides
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 |
Best Practices
✅ DO
- Identify risks early in project planning
- Involve diverse team members in risk identification
- Quantify risk impact when possible
- Prioritize based on risk score and exposure
- Develop specific mitigation plans
- Assign clear risk ownership
- Monitor triggers regularly
- Review and update risk register monthly
- Document lessons learned from realized risks
- Communicate risks transparently to stakeholders
❌ DON'T
- Wait until problems occur to identify risks
- Assume risks will not materialize
- Treat all risks as equal priority
- Plan mitigation without clear trigger conditions
- Ignore early warning signs
- Make risk management a one-time activity
- Skip contingency planning for critical risks
- Hide negative risks from stakeholders
- Eliminate all risk (impossible and uneconomical)
- Blame individuals for realized risks
Comments
Markdown supported