checking-release-readiness
CommunityEvidence-led release decisions, fast.
AuthorFlyFission
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Records a ship, block, defer, or ship-with-risk decision that ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together. Use when a packet, PR, release, dependency change, or agent-authority change approaches merge. Do not use early in development before evidence exists.
Core Features & Use Cases
- Ties the critical release elements into a single decision: baseline, evidence, risk, rollback, monitoring, handoff, and the release outcome.
- Generates and updates essential artifacts like ship.md, risk registers, and escalation paths for releases and changes.
- Useful for change-control packets, dependency updates, and agent-right changes impacting production readiness.
Quick Start
Record a release decision with baseline, evidence, and rollback plan for a merge candidate.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: checking-release-readiness Download link: https://github.com/FlyFission/nuclear-grade-context-engineering/archive/main.zip#checking-release-readiness Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.