RiskScorer

Quantify project or feature risk from specifications and test cases.

1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/farmountain/sdlc_agent_swarm --skill riskscorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: RiskScorer
Source: https://github.com/farmountain/sdlc_agent_swarm/tree/main/vscode-sdlc-swarm/templates/.agents/skills/risk-scorer
Command: npx skills add https://github.com/farmountain/sdlc_agent_swarm --skill riskscorer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill quantifies the risk associated with a project or feature, allowing for dynamic adjustment of governance strictness.

Core Features & Use Cases

  • Risk Assessment: Evaluates inputs like specifications, tests, and domain expert feedback to assign a risk score.
  • Governance Adjustment: Recommends a governance level (LOW, MED, HIGH) based on the calculated risk.
  • Use Case: Before deploying a new feature that impacts production and involves novel technology, use the RiskScorer to determine if strict approval gates are necessary.

Quick Start

Use the RiskScorer skill to assess the risk of the new feature specification.

Frequently Asked Questions about RiskScorer

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

FAQPage Schema
How do I quantify project risk for feature governance and compliance?

To quantify project risk for governance, analyze specifications, test cases, and non-functional requirements. This process evaluates security, reliability, blast radius, and novelty to assign a risk score and recommend an appropriate governance level.

What risk dimensions should I assess before deploying production-impacting features?

When assessing production-impacting features, evaluate risk dimensions including security, reliability, blast radius, and novelty. Domain expert input is also analyzed to determine if strict governance approval gates are necessary for deployment.

How can I determine the right governance level for a new software project?

Determine the right governance level by calculating a risk score from feature specifications and non-functional requirements. The assessment outputs a LOW, MED, or HIGH governance level based on identified security and reliability risks.

Why does novel technology elevate risk assessment scores for governance?

Novel technology elevates risk assessment scores because unknown variables increase potential failure impact. The risk assessment defaults to MED or HIGH governance levels for novel and production-impacting changes to ensure strict compliance and reliability.

Can I adjust governance strictness based on dynamic risk assessment results?

Yes, you can adjust governance strictness by quantifying feature risk. The assessment outputs a LOW, MED, or HIGH governance level, allowing you to dynamically apply the necessary compliance and security approval gates.

Does security impact elevate the risk score for tenancy changes?

Yes, security impacts and tenancy changes elevate the risk score. The risk assessment specifically elevates scores for security or tenancy impacts, ensuring appropriate governance and compliance levels are applied to protect reliability.