operational-closure
CommunityTurn verification into safe rollout decisions
Software Engineering#monitoring#documentation automation#release readiness#runtime verification#rollback planning#CI handoff#operational governance
Authorsoftwaresalt
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It solves the gap between “code is implemented” and “the running system has safely absorbed the change,” ensuring release outcomes are actionable, monitored, and reversible.
Core Features & Use Cases
- Release-readiness artifacts: Produces a closure document capturing readiness, invariants, audits, and explicit post-deploy checks.
- Go/no-go decisioning: Records READY, READY WITH CONDITIONS, or BLOCKED status based on CI and runtime verification evidence.
- Rollback-ready operational detail: Logs rollback triggers, rollback procedures, ownership, and validation windows for risky changes.
- Capability-pack aware integration: Incorporates agent-intercom messaging, browser-verification evidence, strict-safety proposed actions, and release-observability monitoring plans when those packs are installed.
Quick Start
Ask the AI to run the operational-closure skill in post-deploy mode for a feature release and provide the runtime verification report path so it generates the closure artifact with readiness status, monitoring plan, and rollback triggers.
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: operational-closure Download link: https://github.com/softwaresalt/csv-managed/archive/main.zip#operational-closure 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 471,000+ vetted skills library on demand.