handoff-to-deploy

Promote QA-signed-off releases to deploy control planes behind named-human approval with immutable receipts.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill handoff-to-deploy-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-to-deploy
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/handoff-to-deploy
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill handoff-to-deploy-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Promoting a release to a live environment is an irreversible control-plane action that teams often handle with ad-hoc scripts, long-lived secrets, and no audit trail. This Skill enforces a gated deploy handoff: it blocks until a named human approves, mints short-lived OIDC credentials, and emits an immutable receipt tying the release to its approver. ## Core Features & Use Cases - Mandatory named-human approval gate: Blocks on a synchronous approval from a named individual with release authority; agent confidence never substitutes for the gate. - Short-lived OIDC credentials: Mints keyless, environment-scoped tokens that expire when the job ends instead of using long-lived secrets. - Idempotent immutable receipt: Keys the handoff on (idempotency_key, release_ref) so replays return the existing receipt and never double-deploy; emits receipt_id, status, approver, and audit_id validated against a JSON schema. - SAGA compensation: Failed handoffs are never retried in place; they are reversed by the handoff-revoke compensating action. - Use Case: In the S6 stage of a delivery pipeline, after qa-validate returns a pass verdict with evidence, use this Skill to promote the release to production with a named approver and a full audit trail. ## Quick Start Hand off the QA-approved release to the deploy control plane with a named approver and an idempotency key, then return the handoff receipt.

Frequently Asked Questions about handoff-to-deploy

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

FAQPage Schema
How do I gate a production deploy behind a human approval?▼

Require a synchronous named-human approval before the deploy handoff executes. The approver's identity is captured and logged under the stage audit_id, and the handoff blocks on the human queue until approval is recorded.

How to deploy to cloud environments without long-lived secrets?▼

Mint short-lived OIDC tokens scoped to the target environment by exchanging a signed identity JWT for temporary credentials. These keyless tokens expire when the job ends, so leaked credentials are useless outside the execution window.

How do I prevent duplicate deployments on pipeline retries?▼

Key the deploy handoff on an idempotency_key combined with the release_ref. A replay with the same key returns the existing immutable receipt instead of triggering a second deploy.

What happens when a deploy handoff fails?▼

A failed handoff is never retried in place because the action is irreversible. It is compensated by the handoff-revoke SAGA action, which reverses the handoff within the compensation window.

When should I not use a gated deploy handoff skill?▼

Do not use it to author CI/CD pipelines or runbooks, run tests, or validate production SLOs. It only executes the gated handoff and receipt; use dedicated skills for pipeline authoring and SLO validation.