ship

Generate a release-readiness handoff document with scope, evidence, risks, and failure routes.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill ship-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/ship
Command: npx skills add https://github.com/YeaChan05/Remittance --skill ship-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After verification and review, this process generates a concise, auditable handoff that captures release scope, supporting evidence, remaining risks, and a clear failure route to guide deployment teams.

Core Features & Use Cases

  • Structured Release Handoff: compiles release scope, evidence, risks, and failure routes into a single document.
  • Verification Traceability: records results and any no-op or DOCUMENT completion status to justify release decisions.
  • Use Case: prior to production rollout, generate a shared document for stakeholders and on-call teams to ensure operational readiness.

Quick Start

Generate a ready-to-share handoff document summarizing the latest verified release for the next deployment window.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I generate a release-readiness handoff summary after verification?

To generate a release-readiness handoff summary, compile the verified release scope, supporting evidence, remaining risks, and explicit failure routes into a single structured document for deployment teams.

What is a release handoff document and what should it include?

A release handoff document is an auditable summary for operational readiness that must include release scope, verification traceability, remaining risks, and clear failure routes to guide deployment teams.

How do I document verification traceability for a go-live handoff?

Document verification traceability by recording test results and any no-op or DOCUMENT completion statuses to justify release decisions within the operational handoff summary.

Can I use this handoff summary for cross-team operational documentation?

Yes, this handoff summary is applicable for cross-team operational documentation, release planning, and go-live handoffs to ensure shared operational readiness among stakeholders and on-call teams.

What is the best way to communicate remaining risks before a production rollout?

The best way to communicate remaining risks is to enforce documenting them alongside release scope and failure routes in a structured, ready-to-share handoff document for stakeholders.

Why does my deployment team need an explicit failure route in the handoff summary?

An explicit failure route in the handoff summary guides deployment teams during production rollout by providing clear, auditable fallback actions if the verified release encounters issues.