go-live

Automate production go-live workflows with validation, pre-flight checks, and secret rotation.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/venturecrane/crane-console --skill go-live
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-live
Source: https://github.com/venturecrane/crane-console/tree/main/.agents/skills/go-live
Command: npx skills add https://github.com/venturecrane/crane-console --skill go-live

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launching ventures to production involves tight controls around secret rotation, readiness checks, and deployment orchestration. This Skill codifies the end-to-end go-live process and provides guardrails to prevent accidental launches of unready ventures.

Core Features & Use Cases

  • Automated validation: Validates venture code against config/ventures.json and ensures it is not already launched.
  • Pre-flight checks: Performs golden-path readiness, secret inventory, health checks, and DNS verification.
  • Push & smoke tests: Pushes secrets safely to workers and runs health/auth/Sentry checks before handoff.
  • Governed deployment: Updates ventures.json, records a handoff, and creates a production launch record.

Quick Start

Invoke /go-live {venture-code} to begin the production launch workflow for the specified venture.

Frequently Asked Questions about go-live

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

FAQPage Schema
How do I automate production deployment validation and secret rotation for multiple ventures?

Automated production deployment validation and secret rotation are handled by enforcing pre-flight readiness checks and orchestrating secure secret pushes to workers before launching ventures.

What pre-flight checks are required before launching a venture to production?

Required pre-flight checks for a production launch include golden-path readiness validation, secret inventory verification, health checks, and DNS verification to ensure the venture is fully prepared.

Do I need access to specific external tools to orchestrate a production launch?

Yes, orchestrating a production launch requires access to Infisical for secret management, DNS configuration, health endpoints, and your underlying deployment tooling.

How does the deployment workflow handle secrets rotation and worker updates?

The deployment workflow handles secrets rotation by safely pushing rotated secrets to workers and running health, auth, and Sentry smoke tests before final deployment handoff.

What happens if I try to launch a venture that is already in production?

Automated validation prevents accidental launches by checking the venture code against config/ventures.json and blocking the deployment workflow if the venture is already launched.