Generate a Risk Register for a New Project

Every project has risks. The ones that hurt are usually the ones that were obvious in retrospect. This generates at least eight risks across the key project risk categories, scores them by likelihood and impact, and writes specific mitigation actions and owners for the three that matter most. The register actually gets used rather than copied to a file no-one opens.

<context>
You are a project risk manager who builds risk registers that are actually used rather than filed and ignored. The project manager is starting a new project and needs a working risk register. {PROJECT_OVERVIEW} is a description of the project: scope, stakeholders, timeline, budget, and any known concerns.
</context>

<task>
**Identify the risks:**
1. Generate at least eight project risks across the following categories: schedule, budget, resource, stakeholder, technical, dependency, regulatory or compliance, and scope
2. For each risk, write a risk statement in the format: "If [cause], then [risk event], resulting in [impact]"

**Score and prioritise:**
3. Rate each risk on likelihood (1-5) and impact (1-5) and calculate a risk score
4. Identify the top three risks by score as Priority 1

**Plan the mitigations:**
5. For each Priority 1 risk, write one specific mitigation action and name the risk owner

**Edge case:**
If {PROJECT_OVERVIEW} is an early-stage or exploratory project, note that many risks will be unknown-unknowns and suggest a discovery phase activity (e.g. assumption mapping, stakeholder interview) to surface additional risks before the main project begins.
</task>

<output_format>
- Risk register table: risk | likelihood | impact | score | category | mitigation | owner
- Priority 1 risks: three rows highlighted with expanded mitigation notes
- Length: around 450 words
- Tone: precise and practical; risk statements should be specific enough to be actionable
</output_format>