Forge-Risk-Assessment

Identifies, scores, and treats project risks in a maintained risk register.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-risk-assessment-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Risk-Assessment
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Risk-Assessment
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-risk-assessment-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects often fail because delivery, technical, and operational risks stay implicit until they materialize as incidents. This Skill makes uncertainty explicit by producing a maintained risk register where every risk has an owner, a likelihood/impact score, a treatment decision, and a review trigger. ## Core Features & Use Cases - Structured Risk Method: A seven-step workflow covering context establishment, identification, analysis, evaluation, treatment, recording, and monitoring. - Risk Register Output: Every risk is recorded with cause, consequence, score, treatment (mitigate, transfer, avoid, accept), owner, and review trigger. - SDLC Integration: Feeds risk severity into prioritisation, solution architecture decisions, and phase-gate go/no-go evidence. - Use Case: During the Design phase, a Software Architect uses this Skill to evaluate solution risks, record treatments for each, and hand residual-risk evidence to the release readiness review. ## Quick Start Ask the AI to run a risk assessment on the current project scope and architecture, producing a risk register with owners, scores, treatments, and review triggers.

Frequently Asked Questions about Forge-Risk-Assessment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a project risk register?▼

Run the seven-step method: establish context and risk appetite, identify risks by dimension, score likelihood and impact, evaluate against appetite, select treatments, record the register, then monitor on triggers. Each risk gets an owner, score, treatment, and review trigger.

What risk treatment options does a risk assessment support?▼

Four standard treatments are supported: mitigate, transfer, avoid, or accept. Each treatment decision is recorded with an owner and a due action, and acceptance is an explicit Product Owner decision rather than a silent default.

When should risk assessment happen in the SDLC?▼

Use it during Specify to establish project viability and a risk baseline, during Design to evaluate solution risks, when material changes or new dependencies appear, and at phase gates as go/no-go evidence.

Does risk assessment cover security threat modelling?▼

No. Security-specific threat analysis of a design is owned by Forge-Threat-Modelling, whose findings feed into this risk register. This Skill covers delivery, technical, operational, organisational, and compliance risk dimensions.

What are the limitations of a qualitative risk register?▼

Likelihood and impact are scored on an agreed qualitative scale rather than quantified financially, so confidence and information gaps must be noted per risk. It also does not execute contingency plans or assess accumulated technical debt.