/risk - Risk Assessment

Assess risks in code, implementation plans, or project scope.

Usage

/risk [target] [type]

Arguments:

• target - Code path, feature description, or "sprint" for sprint risks
• type - (optional) Risk type: technical, security, schedule, scope

Examples

/risk src/payments/
/risk "Adding real-time notifications feature"
/risk sprint
/risk src/auth/ security

What It Does

1. Identifies risks across dimensions:

   • Technical: Complexity, dependencies, unknowns
   • Security: Vulnerabilities, data exposure
   • Schedule: Estimation accuracy, blockers
   • Scope: Creep potential, unclear requirements

2. For each risk provides:

   • Likelihood (high/medium/low)
   • Impact (high/medium/low)
   • Mitigation strategies
   • Early warning indicators

Output Format

## Risk Assessment: {target}

### Risk Summary
| Risk Level | Count |
|------------|-------|
| High       | X     |
| Medium     | Y     |
| Low        | Z     |

### High Risks

#### 1. {Risk Title}
- **Category:** Technical/Security/Schedule/Scope
- **Likelihood:** High/Medium/Low
- **Impact:** High/Medium/Low
- **Risk Score:** {likelihood × impact}

**Description:**
{What could go wrong}

**Indicators:**
- {Early warning sign 1}
- {Early warning sign 2}

**Mitigation:**
1. {Action to reduce likelihood}
2. {Action to reduce impact}

**Contingency:**
{What to do if risk materializes}

### Medium Risks
{Similar format}

### Recommendations
1. {Most important action}
2. {Secondary action}

### Risk Register
| ID | Risk | Score | Owner | Status |
|----|------|-------|-------|--------|
| R1 | {risk} | {score} | {who} | Open |

Skill Used

skills/analysis/risk/

When to Use Agent Instead

Use the Project Manager agent when:

• Sprint-level risk planning
• Risk tracking over time
• Stakeholder communication about risks
• Risk mitigation tracking