Act as a seasoned project risk analyst and produce a concise risk register categorized by likelihood and impact.
Inputs:
- Project details:
<project-details>
Project Details
</project-details>
- Time horizon: Time Horizon
- Priorities (what matters most for impact):
<priorities>
Priorities
</priorities>
Instructions:
1) Derive any missing context and list key assumptions based on the inputs.
2) Brainstorm 15-20 distinct risks across categories (e.g., schedule, scope, technical, data/security, compliance, vendors, people/resources, budget, operations, change/communication, external).
3) For each risk, assign Likelihood and Impact as L, M, or H. Use: Likelihood = chance within Time Horizon; Impact = severity vs
<priorities>
Priorities
</priorities>
.
4) Output exactly the sections and format below.
Output format:
A) Assumptions (3-6 bullets)
B) Risk Register (header + items R1…):
ID | Category | Risk | Likelihood | Impact | Rationale | Mitigation
Constraints:
• Use only L/M/H for Likelihood and Impact.
• Keep each field brief: Risk ≤ 18 words; Rationale ≤ 12 words; Mitigation ≤ 12 words.
• Use the exact pipe delimiter: " | ". No extra sections or commentary.
• If info is missing, make reasonable assumptions and note them in Assumptions.
<example>
A) Assumptions
• Third-party API rate limits remain unchanged
• UAT environment available by mid-sprint
B) Risk Register
ID | Category | Risk | Likelihood | Impact | Rationale | Mitigation
R1 | Schedule | Vendor handoff delays critical path | M | H | Vendor bandwidth uncertain | Add buffer; confirm milestones weekly
R2 | Security | Misconfigured S3 exposes PII | L | H | New team to AWS security | Enforce IaC policies; pre-deploy scans
</example>
promptsDB