ship-it

Audits launch readiness, reviews build-state maps, syncs Linear backlog items, waits for human approval before ship handoff.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill ship-it-cleanexpo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/CleanExpo/Pi-Dev-Ops/tree/main/skills/ship-it
Command: npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill ship-it-cleanexpo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launching a product requires more than feature-by-feature shipping; teams need a coordinated, multi-lens readiness audit that produces a prioritized, safe backlog before the build and ship machinery starts.

Core Features & Use Cases

  • Pre-flight governance gate: Loads the immutable launch charter first and enforces that no audit, review, or sync violates it.
  • Build-state and pipeline-stage audit: Runs a bulk project scan to map current build state and pipeline stages into date-stamped artifacts.
  • Aggregated multi-lens review and propose-only enhancements: Produces a consolidated review and proposes strengthen/de-bloat/security changes without building.
  • Linear backlog sync with existing contract markers: Creates de-duplicated Linear issues in the correct project, marking only safe/reversible work as build-ready using the existing contract signals (status Ready for Pi-Dev + label pi-dev:autonomous).
  • Human stop/go handoff: Stops after presenting a one-screen summary, then hands off to the existing ship-chain/tao-loop/ship-release on explicit go, without re-implementing build/test/ship.

Quick Start

Run the launch crew by triggering the skill with the intent ship-it or run the launch-ready pre-flight to generate the audit artifacts and the Linear-ready backlog, then approve to hand off to the existing ship chain.

Frequently Asked Questions about ship-it

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

FAQPage Schema
How do I run a launch readiness audit before starting the build and ship process?▼

A launch readiness audit runs a charter-governed pre-flight scan to map build state and pipeline stages into date-stamped artifacts, followed by a multi-lens review to propose enhancements before any build steps execute.

Can I sync a prioritized backlog to Linear using existing contract markers?▼

Yes, backlog sync to Linear creates de-duplicated issues in the correct project, marking only safe and reversible work as build-ready using existing contract signals like status Ready for Pi-Dev and the pi-dev:autonomous label.

What is a multi-lens review for product launch readiness?▼

A multi-lens review for launch readiness consolidates project assessments to propose strengthen, de-bloat, and security changes without building, ensuring all proposals comply with an immutable launch charter.

Does the launch readiness pre-flight gate require human approval before handing off to ship-chain?▼

Yes, the pre-flight process stops after presenting a one-screen summary and requires explicit human go approval before delegating any work to downstream ship-chain, tao-loop, or ship-release workflows.

Do I need a launch charter before running a GitHub-driven launch readiness workflow?▼

Yes, you must load an immutable launch charter first to establish governance, ensuring no audit, review, or backlog sync violates the defined constraints before producing date-stamped artifacts.

Best way to prepare a safe and reversible backlog before shipping a product?▼

The best way is running a propose-only enhancement pass that aggregates review findings and syncs only safe, reversible items to Linear using existing contract markers, stopping for human approval before the ship chain.