Risk Register Skill

This skill produces a complete risk register for a project, programme, or product. Output follows standard risk management practice with likelihood × impact scoring, RAG status, a risk heat map, and specific mitigation and contingency plans. Ready to share with a project board, steering committee, or programme office.

Required Inputs

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

• Project or product name
• Project stage (discovery / delivery / launch / live / programme-level)
• Key objectives — what is the project trying to achieve?
• Known risks — anything already on the team's radar (even informal concerns count)
• Key dependencies — external vendors, teams, systems, or regulatory approvals
• Deadline or milestone sensitivity — are there hard dates that cannot move?
• Audience — who will read this? (internal team / executive steering / external board / regulator)

Output Structure