Run any Skill in Manus with one click

Get Started

assess-risk

Stars5

Forks3

UpdatedJune 29, 2026 at 13:47

Assess pre-deployment risk with rollback plans

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

leifericf

leifericf/agentic-sdk

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	assess-risk
description	Assess pre-deployment risk with rollback plans
user-invocable	false

assess-risk

Pre-deployment risk assessment for a release or change. Ship's release-risk recipe, not a planning dimension, despite the name.

Procedure

Read the dispatched inputs: a PR or diff summary, release notes or change description, feature-flag or config change, and prior incidents or SLOs.
Gather context, at most three questions, preferring pick-one (rollout strategy, blast radius) and binary (confirm non-negotiables).
Summarize the change: what changes, what systems are touched, any data-shape changes.
Assess blast radius: who and what can be affected, worst-case impact.
Map external and internal dependencies and their expected failure behavior.
Design the rollout plan: strategy (all-at-once, staged, canary, feature flag), steps, guardrails.
Design the monitoring plan: key signals, thresholds, where to watch.
Design the rollback plan: triggers, steps, expected recovery time.
Build the risk register: each risk with likelihood, impact, mitigation, detection method, owner.
Define go/no-go criteria and render the decision: go, go with conditions, or no-go pending.
Write ~/.agentic-sdk/<project>/artifacts/ops/YYYY-MM-DD_risk_<change_slug>.md with: Metadata, Change Summary, Blast Radius, Dependencies, Rollout Plan, Monitoring Plan, Rollback Plan, Risk Register, Go/No-Go Criteria, Open Questions, Decision. Slug: lowercase, hyphens, descriptive.

Boundaries

Owns pre-deployment production risk for a release. analyze-root-cause owns incident root cause; assess-rollout owns feature rollout planning during feature work. Reached by ship.

Return

One line: the artifact written and the go/no-go decision, or blocked: <reason>.

More from this repository

same repository

check-style

leifericf/agentic-sdk

Review dimension for naming, idiom, comment debt, and AI tells against the codified per-language and prose standards. Invoked by reviewer agents over one module shard.

2026-07-045

write-c

leifericf/agentic-sdk

Recipe for writing C in the runtime, module placement and the ownership and control-flow discipline. Invoked by writer agents when a C unit is dispatched.

2026-07-045

write-clj

leifericf/agentic-sdk

Recipe for writing Clojure, Functional Core / Imperative Shell at the function level (namespaces by domain), native wrappers, and the boundary discipline. Invoked when writing Clojure for the project.

2026-07-045

write-elixir

leifericf/agentic-sdk

Recipe for writing Elixir, pure functions in modules as the core and GenServer plus OTP as the shell, supervision trees, and NIF discipline for the C and Zig edge. Invoked when writing Elixir for the project.

2026-07-045

write-prose

leifericf/agentic-sdk

Recipe for any English the agent produces in this project, commits, comments, docstrings, ADRs, design docs, skill bodies, changelog, error messages, project guides. Optimizes for terse, humanized prose with no em dashes and no AI tells. Invoke for any prose-writing activity.

2026-07-045

write-zig

leifericf/agentic-sdk

Recipe for writing Zig, native bodies and edge wrappers, the allocator and lifetime discipline, and the hot-path rules. Invoked when writing or editing any Zig source.

2026-07-045

name	assess-risk
description	Assess pre-deployment risk with rollback plans
user-invocable	false

assess-risk

Pre-deployment risk assessment for a release or change. Ship's release-risk recipe, not a planning dimension, despite the name.

Procedure

Read the dispatched inputs: a PR or diff summary, release notes or change description, feature-flag or config change, and prior incidents or SLOs.
Gather context, at most three questions, preferring pick-one (rollout strategy, blast radius) and binary (confirm non-negotiables).
Summarize the change: what changes, what systems are touched, any data-shape changes.
Assess blast radius: who and what can be affected, worst-case impact.
Map external and internal dependencies and their expected failure behavior.
Design the rollout plan: strategy (all-at-once, staged, canary, feature flag), steps, guardrails.
Design the monitoring plan: key signals, thresholds, where to watch.
Design the rollback plan: triggers, steps, expected recovery time.
Build the risk register: each risk with likelihood, impact, mitigation, detection method, owner.
Define go/no-go criteria and render the decision: go, go with conditions, or no-go pending.
Write ~/.agentic-sdk/<project>/artifacts/ops/YYYY-MM-DD_risk_<change_slug>.md with: Metadata, Change Summary, Blast Radius, Dependencies, Rollout Plan, Monitoring Plan, Rollback Plan, Risk Register, Go/No-Go Criteria, Open Questions, Decision. Slug: lowercase, hyphens, descriptive.

Boundaries

Owns pre-deployment production risk for a release. analyze-root-cause owns incident root cause; assess-rollout owns feature rollout planning during feature work. Reached by ship.

Return

One line: the artifact written and the go/no-go decision, or blocked: <reason>.