ship

Orchestrate batch story shipping with waves, git worktrees, and gated QA.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill ship-danhannah94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/danhannah94/claymore-plugins/tree/main/hl/skills/ship
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill ship-danhannah94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end shipping of a batch or epic by coordinating waves of stories, spawning per-branch agent worktrees, and applying gated QA and deployment steps.

Core Features & Use Cases

  • Topological-wave planning to determine execution order and prevent conflicts.
  • Spawn parallel feature agents in dedicated git worktrees per wave, enabling isolated experimentation.
  • Conditional QA backed by a per-project QA backend (test-env+Crucible or headless-preview+dev-auth) to gate visual vs. backend work.
  • Optional deploy and migrate phase plus batch review and merge workflows for production readiness.
  • Use Case: Shipping an epic with multiple stories across teams, with dependencies and risk-guarded handoffs.

Quick Start

Provide a batch spec or path to the epic design doc and invoke /hl:ship to begin processing.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate epic deployment and batch shipping for multiple stories?

Automated batch shipping orchestrates waves of stories using topological sorting for dependency resolution and parallel execution via git worktrees. This coordinates per-wave agents and gated QA to ensure safe, auditable epic deployments.

How does git worktree orchestration work for parallel AI agent execution?

Git worktree orchestration spawns dedicated feature branches for isolated experimentation per wave. By applying topological sorting to manage dependencies, multiple AI agents can execute stories in parallel without causing branch conflicts.

What's the best way to manage dependency resolution when deploying a multi-story batch?

Managing dependency resolution in a multi-story batch requires topological-wave planning to determine execution order. This prevents conflicts by sequencing dependent stories correctly across waves before applying gated QA and deployment steps.

Can I use gated QA to gate visual vs. backend work in an automated deployment pipeline?

Conditional gated QA gates visual versus backend work by backing checks with a per-project QA backend. It utilizes test-env with Crucible or headless-preview with dev-auth to validate specific work types before merging.

Do I need a batch spec or epic design doc to start automated batch shipping?

Yes, you need to provide a batch spec or a path to an epic design doc to start. This input initializes the orchestration of waves, dependency resolution, and parallel feature agents for your multi-story batch.

Why should I use PR-based collaboration for post-merge validation in batch shipping?

PR-based collaboration enforces post-merge validation to ensure safe, auditable shipping across teams. It guards risk during handoffs by validating each story within a batch before finalizing the optional deploy and migrate phases.