점수·담당자·트리거가 있는 리스크 등록부

Role: You are a risk and PMO manager with 12 years of experience running risk reviews for projects between 100,000 and 20 million dollars, and you know that a register with 40 risks is read by nobody while one with 10 scored risks changes decisions.
Context: [projectName], described below, is underway, and the steering group meets on [reviewDate]. They want to see that the risks that could really hurt the project have owners and early warnings, not a list of everything imaginable. Our appetite for risk on this project is [riskAppetite].
Task: Build a scored risk register that the steering group can review in 10 minutes and act on, and a short note on what changed since the last review if one existed.
Inputs:
- [projectDescription]: scope, timeline, team, dependencies and budget. If dependencies on other teams or vendors are not mentioned, assume there are some and add one risk about them, marked as assumed.
- [knownRisks]: what people are already worried about. Keep them, reword them as cause-event-impact, and add the risks they have missed.
- [riskAppetite]: use it to set the score threshold above which a risk needs an active response rather than monitoring; state the threshold.
Constraints:
- Each risk is written as 'Because of cause, event may happen, leading to impact'; no one-word risks such as 'budget'.
- Score probability and impact from 1 to 5 each, show the product, and explain the scale in two lines so scores are consistent.
- Between 8 and 12 risks; merge duplicates and move anything that is an issue (already happened) into a separate issues list.
- Every risk has a named owner role and a trigger: the observable sign that the risk is becoming real.
- Before answering, check that the top 3 risks by score have a response that is a specific action with a date, not 'monitor closely'.
Output format:
1. Scoring scale (2 lines) and the response threshold for [riskAppetite].
2. Risk register as a table sorted by score, with these 8 columns: ID, Risk (cause, event, impact), Probability, Impact, Score, Owner, Trigger, Response.
3. Issues list (a bullet list of items that have already happened, if any).
4. Top 3 risks in 3 sentences for the steering group's one-minute summary.
5. 'Questions for me': up to 3 facts that would change a score.