Help us improve
Share bugs, ideas, or general feedback.
From nuclear-grade
Records and audits release-readiness decisions (ship, block, defer, ship-with-risk) by tying together baseline, evidence, residual risk, rollback, monitoring, and handoff. Use when a change approaches merge or release.
npx claudepluginhub flyfission/nuclear-grade-context-engineering --plugin nuclear-gradeHow this skill is triggered — by the user, by Claude, or both
Slash command
/nuclear-grade:checking-release-readinessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Release readiness is a careful, audited decision you write down. It is not a mood. It ties seven things together before a candidate becomes the accepted version: the baseline (the version everyone agreed is correct), the evidence status, the leftover risk, the rollback plan, the monitoring plan, the handoff, and the release decision itself.
Audits release readiness by classifying risk level, checking verification evidence, and confirming operational readiness before deploying or merging.
Routes AI-assisted work by consequence: classify changes as Quick or Standard-plus, build change records, and plan proof. Use at the start of any change, repo adoption, or release call.
Evaluates build readiness for external testing, certification, store submission, or launch with binary go/no-go gates and waiver tracking.
Share bugs, ideas, or general feedback.
Release readiness is a careful, audited decision you write down. It is not a mood. It ties seven things together before a candidate becomes the accepted version: the baseline (the version everyone agreed is correct), the evidence status, the leftover risk, the rollback plan, the monitoring plan, the handoff, and the release decision itself.
ship.md, verification.md, trace.md, the pull request status, the CI status, the rollback plan, the monitoring plan, and the open risks.docs/02-operating-system/change-control-packets.md.staying-on-mission.ship.md.ship.md states the release decision, the rollback, and the monitoring.This skill is an original release-readiness workflow influenced by public lifecycle, configuration, software assurance, and secure development sources mapped in docs/00-standards-foundation/source-map.md. It does not grant production suitability.