ship

Coordinate the PDLC Operation phase from Ship through Reflect with gated handoffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the Operation phase (Ship → Verify → Reflect) for the current feature.

Core Features & Use Cases

  • Orchestrates Ship, Verify, and Reflect sub-phases in strict sequence with gated handoffs.
  • Provides artifact governance: STATE.md, DEPLOYMENTS.md, and episode files to ensure traceability.
  • Automates logging and role-based prompts to reduce manual overhead during release cycles.

Quick Start

Run the /pdlc ship command and follow the prompts to advance from Ship to Reflect.

Frequently Asked Questions about ship

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

FAQPage Schema
What is a gated release process for feature deployment?

A gated release process for feature deployment enforces strict sequential execution across sub-phases like Ship, Verify, and Reflect. It uses role-based handoffs and logs to guarantee traceability and compliance during the operation phase.

How do I automate the operation phase from ship to reflect?

You can automate the operation phase from ship to reflect by running the ship command. It orchestrates the sub-phases in strict sequence, automating logging and role-based prompts to reduce manual overhead during release cycles.

How do I maintain traceability and artifact governance during a release?

To maintain traceability and artifact governance during a release, the process generates and manages specific files like STATE.md, DEPLOYMENTS.md, and episode files. These artifacts ensure every deployment action is logged and compliant.

Can I skip the verify sub-phase when shipping a feature?

No, you cannot skip the verify sub-phase when shipping a feature. The process orchestrates Ship, Verify, and Reflect in a strict sequence with gated handoffs to ensure a disciplined release and full compliance.

What's the best way to enforce role-based handoffs in CI-CD?

The best way to enforce role-based handoffs in CI-CD is to use an automated operation phase coordinator. It prompts specific roles sequentially and logs each transition, guaranteeing strict order execution and reducing manual release overhead.