skills.rest
FlyFission
FlyFissionCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rating-change-risk

Determine Nuclear-grade change mode from stakes, reversibility, exposure, unknowns, and proofs.

33|Updated May 24, 2026
Search Tags:#workflow#evidence#risk-management#escalation#change-management#mode-selection#nuclear-grade
One-click install
npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill rating-change-risk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rating-change-risk
Source: https://github.com/FlyFission/nuclear-grade-context-engineering/tree/main/skills/rating-change-risk
Command: npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill rating-change-risk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Controls and clarifies how to apply risk-aware decision-making to changes, ensuring the right level of scrutiny matches the stakes.

Core Features & Use Cases

  • Mode selection: maps change context to Quick, Standard, or stronger human-reviewed modes.
  • Evidence & escalation planning: defines required records, triggers, and guardrails for different risk levels.
  • Governance alignment: supports code, docs, dependencies, AI prompts, and release changes with consistent risk discipline.

Quick Start

Provide the change request, context, and affected artifacts to receive a mode recommendation with required evidence.

Frequently Asked Questions about rating-change-risk

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

FAQPage Schema
How do I determine the right risk level for a software change request?▼

Change request risk levels are determined by evaluating stakes, reversibility, exposure, and unknowns to select a matching governance mode and evidence bar.

What is change management mode selection for code and dependency updates?▼

Change management mode selection maps change context to Quick, Standard, or human-reviewed modes, tailoring escalation triggers and required record files to the risk level.

How do I set escalation triggers and guardrails for high-risk release changes?▼

Escalation triggers and guardrails for release changes are defined by matching the exposure and reversibility of the update to a nuclear-grade mode with required proofs.

Can I apply risk management workflows to AI prompt and documentation changes?▼

Yes, risk management workflows apply to AI prompts, documentation, and code changes by consistently calibrating required evidence and guardrails to the change stakes.

What is the best way to align evidence requirements with change exposure and unknowns?▼

The best way to align evidence requirements is to evaluate unknowns and exposure, then apply a nuclear-grade mode that dictates the exact proof and record file needed.

When should I not use a quick mode for change management?▼

Quick mode should be avoided when change requests involve high stakes, low reversibility, or significant unknowns, requiring stronger human-reviewed modes with strict guardrails.

Related Skills

Explore More Software Engineering Skills→
SSiertsemaSSiertsema

impact-analysis

Analyze proposed changes across a traceability graph to identify affected artifacts and risks.

Community
Advanced
vm-wylburvm-wylbur
1

cleanup

Analyze unstaged and untracked files and execute deletions after user approval.

Community
Advanced
kkmookheykkmookhey
7

evidence

Collects and stores timestamped compliance evidence snapshots for audits in cloud environments.

Community
Intermediate
StepowskiEricStepowskiEric
1

thoroughness-check-etto-skill

Evaluate task risk and select Fast, Balanced, or Thorough execution modes.

Community
Advanced