go-live-checklist

Consolidates go-live readiness criteria into a GO, CONDITIONAL GO, or NO-GO decision framework.

2|1|Updated Apr 15, 2026

Search Tags:#checklist #deployment #sign-off #risk-management #decision-framework #go-live #release-readiness

Ready to run

npx skills add https://github.com/erphq/skills --skill go-live-checklist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-live-checklist
Source: https://github.com/erphq/skills/tree/main/templates/03-org-1k-plus/go-live-checklist
Command: npx skills add https://github.com/erphq/skills --skill go-live-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Go-Live Checklist consolidates readiness criteria across data, configuration, integration, testing, training, and operations into a single go/no-go decision framework, reducing last-minute surprises before launch.

Core Features & Use Cases

Unified readiness gate for go-live across all workstreams (data, config, integration, testing, training, support).
Structured decision rules: GO, CONDITIONAL GO, or NO-GO based on severity and mitigations.
Executive sign-off templates and playbooks to accelerate decision-making.
Use Case: When a deployment is within two weeks of go-live, the checklist helps determine readiness and trigger hypercare planning.

Quick Start

Initiate the Go-Live Checklist review with all workstream leads to determine readiness two weeks before planned go-live.

Frequently Asked Questions about go-live-checklist

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

FAQPage Schema

What is a go-live readiness checklist and when should I use it?▼

A go-live readiness checklist consolidates criteria across data, configuration, integration, testing, training, and operations into a single decision framework. Initiate this review with workstream leads two weeks before your planned enterprise deployment to determine launch readiness.

How do I make a GO or NO-GO decision for an enterprise deployment?▼

Make a GO, CONDITIONAL GO, or NO-GO deployment decision by applying structured decision rules based on issue severity and available mitigations. The framework enforces evidence-based sign-offs and documented remediation plans to support the final executive decision.

What workstreams should be included in a release readiness sign-off?▼

Release readiness sign-off should cover data migration, configuration, integrations, testing, training, and operations workstreams. Consolidating these areas into a unified readiness gate ensures comprehensive risk management and prevents last-minute surprises before launch.

Can I use a conditional go-live decision for my deployment?▼

Yes, you can use a CONDITIONAL GO decision when deployment risks are identified with acceptable mitigations. The framework allows a conditional launch by enforcing severity-based gating and requiring documented remediation plans for any open issues across the enterprise workstreams.

Does this go-live checklist support hypercare planning after sign-off?▼

Yes, the go-live checklist helps determine readiness and triggers hypercare planning once a decision is made. By consolidating readiness criteria and executive sign-off templates, it accelerates the transition from deployment decision to post-launch operational support.

Best way to manage deployment risk management across multiple workstreams?▼

The best way to manage deployment risk across workstreams is a unified decision framework that applies severity-based gating and documented remediation plans. This approach consolidates evidence-based sign-offs across data, testing, and operations into a single release readiness gate.