Identifying Project Risks

Scan plans for risks backed by concrete evidence — not speculation.

HARD-GATE

• Every risk must cite specific evidence (task, requirement).
• Do not flag everything high-risk; use likelihood/impact matrix honestly.
• Provide at least one concrete mitigation per risk.

Core Process

1. Receive plan (tasks, tickets, PRD, sprint).
2. Scan for six patterns: dependency chains, single points of failure, ambiguous requirements, external dependencies, capacity/resource issues, technical uncertainty.
3. Classify each risk: Likelihood (High/Medium/Low), Impact (High/Medium/Low), Proximity (Immediate/Near-term/Future).
4. Suggest mitigation (prevention, contingency, owner).
5. Validate: remove risks lacking direct evidence.
6. Output risk register.