generate-risk-register

generate-risk-register

Triggers

Russian: «сформируй реестр рисков», «подготовь risk register», «обнови реестр рисков» English: "generate risk register", "create risk register", "update risk register"

Language Detection

Determine the language of the user's request:

• If the request is in Russian → use templates with -ru suffix
• Otherwise → use templates with -en suffix

All output (headings, labels, comments, instructions) must match the detected language.

---

1. Input Data

Initial mode (phase 1)

Data	Required	Source	Notes
Project charter (project-charter.md)	yes	knowledge	Primary context: goal, scope, timeline, budget, constraints, assumptions
Project type / industry	no	chat or knowledge	Used to select industry-typical risks. If not specified — agent infers from charter
Additional context	no	chat	User comments on specific risks

Detailed mode (phase 2)

Data	Required	Source	Notes
Project charter (project-charter.md)	yes	knowledge	Project context
Project plan (project-plan.md)	yes	knowledge	WBS, timeline, resources, dependencies — source of new risks
Risk register v1 (risk-register.md)	yes	knowledge	Output of initial mode — base for update
Additional context	no	chat	New risks identified by the user

If required data is missing — request using this template:

To generate the risk register, the following is required:
— Initial mode: approved project charter (project-charter.md).
— Detailed mode: charter + project plan (project-plan.md) + current risk register (risk-register.md).
Available data: [list what is available].
Missing: [be specific].

---

2. Execution Algorithm

1. Determine mode. If the user has not specified — infer from context: project plan present → detailed, charter only → initial. If ambiguous — ask.
2. Verify input data. Minimum data for the selected mode is present → step 3. Missing → request using the template from §1. Do NOT generate a placeholder or sample register.
3. Read the template risk-register-ru.md or risk-register-en.md from project knowledge (based on detected language).
4. Identify risks.
   • Initial: Analyze the charter from scratch — goal, scope (included and excluded), timeline, budget, constraints, assumptions, team composition. For each charter section evaluate: what could go wrong? Use categories from the reference table (§3). Recommended count: 5–10 risks. Do not automatically copy the top-3 risks from the charter — perform an independent analysis (charter risks may enter the register if confirmed by analysis).
   • Detailed: Use register v1 as the base. Analyze the project plan: WBS (which work packages are highest risk?), critical path, dependencies, resource constraints. Add new risks. Update assessments of existing risks (probability/impact may have changed). For each risk — link to WP-xxx from the plan, assign a specific owner from project-plan. Specify actions concretely.
5. Assess each risk using the scale from the reference table (§3): category, probability (H/M/L), impact (H/M/L), level, strategy (Avoid/Mitigate/Transfer/Accept). Level is calculated strictly by the table below — not by intuition or proximity to adjacent cells: