ship

Create epics, stories, tasks, and plan files from a single ship command.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill ship-kelsi-andrewss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/kelsi-andrewss/claude-multi-agent-pipeline/tree/main/skills/ship
Command: npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill ship-kelsi-andrewss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of an epic, stories, tasks, and execution plans from a single command, reducing manual setup and handoffs in software delivery.

Core Features & Use Cases

  • Create epics, stories, and tasks from a slash command and automatically generate plan files.
  • Launch and orchestrate execution across multiple agents, with optional quick or argued validation modes.
  • Provide a structured workflow for planning, review, and integration, all within a repeatable pipeline.

Quick Start

Type /ship with a title and features, or point to an existing plan or PRD file to init the pipeline.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate creating epics, stories, and tasks for a software delivery pipeline?

Automated software delivery pipelines orchestrate epic, story, and task creation from a single command. This skill generates plan files, execution launches, and integration steps automatically, reducing manual setup and handoffs across cross-agent coordination workflows.

What is end-to-end software pipeline automation and when do I need it?

End-to-end software pipeline automation handles scoping, planning, and execution from a single command. Teams need it when they want to enforce structured planning and cross-agent coordination across multiple stories without manual handoffs between development phases.

Can I use an existing PRD or plan file to initialize an automated delivery pipeline?

Automated delivery pipelines can initialize from an existing PRD or plan file. You provide the file reference to the command, and the pipeline generates corresponding epics, stories, tasks, and execution plans based on that input.

What's the best way to validate execution plans across multiple agents before deployment?

Validating execution plans across multiple agents is supported through quick or adversarial argue validation modes. These modes enforce structured review within the pipeline, ensuring deployment-ready outputs with verified plan files, tasks, and integration steps.

Does automated scoping and planning work for teams needing cross-agent coordination on multiple stories?

Automated scoping and planning supports cross-agent coordination across multiple stories and tasks. It orchestrates execution launches from a single command, enforcing structured planning workflows that scale across teams without manual intervention.

What are the limitations of automating software delivery from a single command?

Automating software delivery from a single command requires structured input for effective scoping and planning. Without a clear title, features, or existing plan file, the pipeline may not generate accurate epics, stories, or execution tasks for cross-agent coordination.