risk-assessment

Identify, evaluate, and mitigate project risks using structured frameworks and risk matrices.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/DTMC-marketplace/governance --skill risk-assessment-dtmc-marketplace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-assessment
Source: https://github.com/DTMC-marketplace/governance/tree/main/skills/risk-assessment
Command: npx skills add https://github.com/DTMC-marketplace/governance --skill risk-assessment-dtmc-marketplace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams proactively identify, evaluate, and plan mitigations for potential risks that could derail project timelines, scope, or quality.

Core Features & Use Cases

  • Risk Identification: Utilizes structured techniques like pre-mortems and assumption surfacing to uncover potential issues.
  • Risk Evaluation: Provides frameworks for assessing likelihood and impact to prioritize risks.
  • Mitigation Planning: Offers strategies and patterns for addressing identified risks.
  • Use Case: Before starting a complex feature development, use this Skill to brainstorm potential technical hurdles, integration challenges, and scope creep possibilities, then document mitigation plans.

Quick Start

Assess the main risks in implementing this feature, evaluating likelihood and impact.

Frequently Asked Questions about risk-assessment

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

FAQPage Schema
How do I identify and evaluate technical risks before starting complex feature development?

Project risk identification uses structured techniques like pre-mortems and assumption surfacing to uncover technical hurdles, while risk evaluation frameworks assess likelihood and impact to prioritize potential blockers. This helps proactively pinpoint scope creep and integration challenges before development begins.

What is a pre-mortem and how does it help with project risk mitigation?

A pre-mortem is a structured risk identification technique that assumes a project has failed and works backward to uncover potential technical hurdles and integration challenges. It helps teams proactively brainstorm and document mitigation plans for identified project blockers before development starts.

How do I plan contingencies for technical debt and complexity in software engineering projects?

Contingency planning evaluates technical debt and complexity by assessing project confidence levels using structured frameworks and risk matrices. This process identifies potential blockers early, allowing teams to formulate targeted mitigation strategies and plan appropriate fallback patterns for project timelines.

Can I use a risk matrix to determine project confidence levels for my development tasks?

Yes, a risk matrix evaluates task-level risks by mapping likelihood and impact to determine overall project confidence levels. This structured framework supports assessing technical risks, evaluating complexity, and identifying blockers during the planning phase of complex features.

What's the best way to surface assumptions that could derail project scope and quality?

Assumption surfacing is a structured risk identification technique used to proactively uncover hidden issues that could derail project scope, timelines, or quality. By evaluating these assumptions against likelihood and impact frameworks, teams can prioritize and plan mitigations for potential scope creep.

When should I not use structured risk assessment frameworks for project planning?

Structured risk assessment frameworks are less necessary for simple, low-complexity tasks where technical debt and integration challenges are minimal. If a project lacks significant blockers or scope creep possibilities, applying risk matrices may add unnecessary overhead to the planning process.