Verify acceptance criteria and evidence to produce a launchReadinessPlan.
npx skills add https://github.com/vTRKA/supervibe --skill shipping-and-launch-vtrka
Please help me install this Agent Skill. Skill: shipping-and-launch Source: https://github.com/vTRKA/supervibe/tree/main/skills/shipping-and-launch Command: npx skills add https://github.com/vTRKA/supervibe --skill shipping-and-launch-vtrka
Shipping changes without clear, command-backed evidence makes it hard to prove launch readiness, coordinate rollout/rollback, and support users after release.
Ask your AI to run a release gate in dry-run mode by providing the change scope, acceptance criteria, target branch/version, and authority, and to return a structured launchReadinessPlan with a BLOCK/ADVISORY/RELEASE decision.
High-intent search queries and answers about installing and using this skill.
You can verify release readiness by checking project scope, git state, version and changelog alignment, and defining rollback actions. This returns a structured launchReadinessPlan that scores confidence against a gate, providing a clear BLOCK, ADVISORY, or RELEASE decision for your production rollout.
Defining a feature rollout involves selecting a strategy like canary, staged, or dark launch, and specifying conditions for safe progression. You also define rollback actions, monitoring metrics, alerts, and post-launch cleanup to prevent uncontrolled merge-event style releases.
Checking alignment for a package publish requires verifying targeted evidence across code graph release surfaces, git state, version, docs, and changelog. The process evaluates this alignment alongside migration needs to determine if the package update is truly ready to release.
Yes, the release readiness process supports feature flags and dark launches by allowing you to define specific rollout strategies and conditions required for safe progression. It evaluates your change scope and monitoring setup to return a structured launchReadinessPlan for these deployment methods.
You assign support ownership and define communication by specifying post-launch cleanup actions as part of your launch readiness plan. This ensures operational changes, support responsibilities, and monitoring alerts are explicitly documented to prevent merge-event style releases.
vTRKAGenerate a parseable gitVersioningPlan for atomic commits and versioning.
kevinnftPlan and execute production launches with staged rollback and monitoring.
BorisserzCoordinate production launches with pre-launch checklists, staged rollouts, monitoring, and rollback.
lalulaliCoordinate product launch readiness and production release execution.
