assess-risky-change-readiness

Assesses safety controls, recovery strategy, evidence, and authorization before consequential changes execute.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill assess-risky-change-readiness-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assess-risky-change-readiness
Source: https://github.com/mtk177a/skills/tree/main/skills/assess-risky-change-readiness
Command: npx skills add https://github.com/mtk177a/skills --skill assess-risky-change-readiness-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Consequential or hard-to-recover changes often cross into execution without verified safety controls, credible recovery plans, or clear authorization. This Skill evaluates whether a high-risk change is genuinely ready to execute, separating confirmed evidence from reported claims and stopping at a read-only readiness or authorization handoff. ## Core Features & Use Cases - Risk-Property Assessment: Evaluates reversibility, recoverability, blast radius, external-state mutation, detectability, authority, and uncertainty rather than relying on category labels. - Evidence Discipline: Classifies every material input as Confirmed, Reported, Inferred, Assumed, or Unknown, and never treats proposed controls or intended backups as verified facts. - Exclusive Completion States: Assigns exactly one of Not applicable, Blocked, Ready for authorization, or Ready for execution handoff, with Blocked taking precedence when material gaps remain. - Use Case: Before running a production database migration, use this Skill to verify the restore drill evidence, abort thresholds, monitoring, and ownership are decision-ready, then produce a handoff naming the production change owner who must still approve the exact run. ## Quick Start Ask the agent to assess whether a planned production change is ready to cross into execution, providing the exact action, target, environment, and any existing controls or approvals.

Frequently Asked Questions about assess-risky-change-readiness

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

FAQPage Schema
How do I check if a production change is ready to execute?▼

Provide the exact action, target, environment, and execution boundary along with any existing controls and approvals. The Skill maps each material risk to prevention, detection, abort criteria, and recovery treatment, then assigns one readiness state: Not applicable, Blocked, Ready for authorization, or Ready for execution handoff.

When should I use a risky change readiness assessment?▼

Use it when material operational, data, security, external-state, irreversibility, or recovery risks require more than an ordinary implementation handoff. Skip it for routine reversible changes, already-authorized implementations with complete controls, completed diff reviews, or failure investigations.

Does this Skill approve or execute the change?▼

No. It records authorization state but never grants approval, runs commands, modifies files, or executes operations. It stops at a read-only readiness or authorization handoff and labels any proposed commands as unexecuted.

What happens when rollback is impossible for a change?▼

The Skill does not invent rollback for irreversible actions. It selects realistic alternatives such as roll-forward, restore, compensation, containment, or explicit acceptance of irreversible loss, and marks the result Blocked if a material irreversible loss lacks an authorized acceptance decision.

Why does an assessment return Blocked even with some controls in place?▼

Blocked takes precedence over authorization status whenever a material readiness gap remains. Reported but unverified rollback procedures, missing abort authority, or approvals covering a narrower scope than the planned action all keep the result Blocked.