ship

Compile verified items and surface remaining risks in ship readiness reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill ship-jukqaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/claude/skills/ship
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill ship-jukqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the final ship checklist and summarize what was verified before sign-off.

Core Features & Use Cases

  • Automates the final ship readiness review by compiling verified items and surfacing remaining risks.
  • Applies during release workflows across software builds, QA, and approval steps to ensure traceable handoffs and consistent sign-off criteria.
  • Outputs a concise, structured ship readiness summary for stakeholders at sign-off.

Quick Start

Run this lane right before sign-off to summarize verified items and remaining risks.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a release readiness checklist before sign-off?

Automate release readiness by running this Skill right before sign-off to compile verified checklist items and surface remaining risks. It reads ship-related checklists and outputs a structured verification summary for stakeholders.

What is ship readiness verification in software release workflows?

Ship readiness verification compiles verified items across software builds, QA, and approval steps to ensure traceable handoffs. It outputs a concise, structured summary of what was verified and what risks remain before final sign-off.

How do I summarize QA verification results for stakeholder approval?

Summarize QA verification results by reading ship-related checklists and generating a structured readiness summary. This surfaces remaining risks and confirmed items, providing consistent sign-off criteria for stakeholder approval.

Can I use this for final sign-off across different software build workflows?

Yes, this applies during release workflows across software builds, QA, and approval steps. It ensures traceable handoffs and consistent sign-off criteria regardless of the specific build process by compiling verified items into a structured summary.

Does this release sign-off tool require any dependencies or components?

No dependencies or components are required to run this release sign-off tool. It operates independently to read ship-related checklists and output a structured verification summary highlighting verified items and remaining risks.