risk-assessor

Assess technical, operational, scalability, security, delivery, and AI/spec ambiguity risks across engineering artifacts.

Updated May 9, 2026
One-click install
npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill risk-assessor-gustavogutierrez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-assessor
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/risk-assessor
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill risk-assessor-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically surface technical, operational, scalability, security, delivery, and AI/spec ambiguity risks early—so you can decide what must be resolved now versus what can be monitored.

Core Features & Use Cases

  • Risk identification across six categories: Finds design and plan vulnerabilities spanning architecture, delivery workflows, operations, security boundaries, and AI/spec uncertainty.
  • Evidence-based classification: Produces a risk register that ties each risk to concrete evidence from the reviewed artifact and flags gaps as EVIDENCE: INSUFFICIENT.
  • Blocking vs acceptable outputs: Distinguishes blocking risks (e.g., security breach or delivery failure likelihood) from acceptable risks, with mitigations for items above medium.
  • Decision traceability artifacts: Recommends complementary artifacts like ADRs, threat modeling, rollout plans, observability plans, technical spikes, and test strategies when relevant.
  • Consistent structured delivery: Generates a structured risk assessment summary and a prioritized risk register with impact/probability/overall scoring.

Quick Start

Use the risk-assessor skill to assess risks in the provided architecture or specification and produce a prioritized risk register with mitigations for blocking items.

Frequently Asked Questions about risk-assessor

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

FAQPage Schema
How do I identify delivery and architecture risks in an engineering spec?

Risk assessment systematically surfaces technical, operational, scalability, security, delivery, and AI/spec ambiguity risks across engineering specs by producing an evidence-based risk register that separates blocking issues from acceptable ones.

What is the best way to prioritize blockers versus acceptable risks during an architecture review?

Prioritizing risks during an architecture review involves applying probability and impact scoring to each identified item, separating blocking risks that require immediate resolution from acceptable risks that can simply be monitored.

How do I assess AI spec ambiguity and security risks without assuming a specific domain context?

Assessing AI spec ambiguity and security risks without domain-specific context requires a generalized framework that scrutinizes failure modes, feasibility signals, and security boundaries to generate a structured risk assessment summary.

Can I generate a risk register with mitigation recommendations for technical and operational vulnerabilities?

Yes, generating a risk register with mitigation recommendations produces a prioritized output that ties each technical and operational vulnerability to concrete evidence and flags any gaps as insufficient evidence.

When do I need to create decision traceability artifacts like ADRs and threat models for risk mitigation?

Decision traceability artifacts like ADRs, threat models, and rollout plans are needed when a risk assessment identifies blocking vulnerabilities that require structured mitigation planning and documented engineering decisions.