ship

Coordinate parallel expert reviews into a rollback-enabled GO/NO-GO ship decision.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate parallel expert reviews from multiple personas to produce a single ship decision.

Core Features & Use Cases

  • Parallel fan-out of three subagents (addy-code-reviewer, addy-security-auditor, addy-test-engineer) running in parallel and merging into a consolidated GO/NO-GO decision.
  • Rollback-enabled governance: when blockers exist, a formal rollback plan is produced and documented.
  • Phase-based workflow: separate orchestration, merge, and rollback phases to ensure traceability and safety.

Quick Start

Invoke the ship workflow on the current change to generate a GO/NO-GO decision with a rollback plan.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I get a formal go/no-go decision before shipping code changes?▼

A formal go/no-go decision is produced by coordinating parallel expert reviews from code, security, and test personas, merging their findings into a consolidated verdict and rollback plan.

How do parallel subagents work for code review and security audits?▼

Parallel subagents work by spawning three distinct expert personas simultaneously to review code quality, security, and tests, then merging their separate reports into a single consolidated decision.

Can I generate a rollback plan automatically when a deployment blocker is found?▼

A rollback plan is generated automatically during the final workflow phase when blockers exist, ensuring rollback-enabled governance and formal documentation before any deployment proceeds.

What is the best way to orchestrate cross-functional reviews for a release?▼

The best way to orchestrate cross-functional reviews is using a three-phase workflow that separates parallel subagent fan-out, consolidated merging of findings, and rollback planning for traceability.

Does the ship workflow require any specific dependencies or external components?▼

The ship workflow requires no external dependencies or components, running entirely as a self-contained orchestration process to evaluate changes and produce a formal release decision.

When should I not use a parallel review orchestration workflow?▼

Parallel review orchestration should not be used for changes that do not require cross-functional evaluation across code quality, security, and tests, as it adds overhead for simple modifications.