risk-manager

Identify, evaluate, and prioritize operational, product, financial, and architectural risks.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill risk-manager-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-manager
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/risk-manager
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill risk-manager-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit risk analysis to help teams identify, quantify, and mitigate product, operational, financial, and architectural risks before decisions are made.

Core Features & Use Cases

  • Map domain boundaries and decision points to clarify risk exposure
  • Separate evidence from assumptions to improve decision confidence
  • Recommend the smallest safe mitigations with clear tradeoffs and ownership
  • Define escalation criteria and monitoring to ensure risk is actively managed

Quick Start

Analyze the task, map the domain-specific risks, separate evidence from assumptions, and propose the smallest safe mitigation with clear ownership.

Frequently Asked Questions about risk-manager

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

FAQPage Schema
How do I identify and quantify product risks before a launch?

Risk analysis for system migrations involves mapping domain boundaries, separating evidence from assumptions, and proposing the smallest safe mitigations with clear ownership to quantify operational and architectural risk tradeoffs.

How do I separate evidence from assumptions during risk analysis?

Operational risk mitigation requires defining escalation criteria, monitoring active risk exposure, and assigning clear ownership to the smallest safe mitigations to ensure quantified risks are actively managed.

What is the best way to map domain boundaries for risk tradeoffs?

Mapping domain boundaries for risk tradeoffs involves identifying decision points across product, operational, financial, and architectural domains to clarify exposure and quantify risk before decisions are made.

Can I use this approach for both process changes and system migrations?

Yes, this risk analysis approach applies to process changes, system migrations, and product launches by identifying, evaluating, and prioritizing operational, product, financial, and architectural risks for any given task.