ship

Orchestrate the spec-to-commit pipeline with phase-by-phase subagents and dry-run mode.

10|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/dixus/claudeframework --skill ship-dixus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/dixus/claudeframework --skill ship-dixus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the full spec → implement → review → fix → commit pipeline to ship features reliably, reducing context switching and drift between phases. It provides structured handoffs, guardrails, and deterministic progress across a multi-agent workflow so teams can ship complex features with confidence.

Core Features & Use Cases

  • End-to-end feature delivery across spec, implement, review, fix, and commit phases with clear handoffs.
  • Dry-run mode to preview scope and complexity before committing resources.
  • Architecture-neutral orchestration where each phase runs in isolated subagents with clean contexts.
  • Branch checkpointing, progress updates after each subagent, and integrated verification before merge.

Quick Start

Invoke the ship skill with a feature description to start the end-to-end pipeline.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I orchestrate a full feature delivery pipeline from spec to commit?

Feature delivery orchestration coordinates the spec, implement, review, fix, and commit phases using deterministic handoffs. It runs each phase in isolated subagents with clean contexts to reduce drift and context switching across the pipeline.

Can I preview the scope of a feature pipeline before committing resources?

Yes, you can preview pipeline scope using the dry-run mode. This mode evaluates the complexity and projected steps of the feature delivery pipeline before allocating actual processing resources to the implementation phase.

How does multi-agent orchestration handle handoffs between implementation and review?

Multi-agent orchestration handles handoffs by running isolated subagents for each phase with clean contexts. It enforces deterministic progress updates and integrated verification before allowing the pipeline to advance to the commit step.

Can I run the feature delivery pipeline without automatically finalizing the commit?

Yes, you can run the pipeline without finalizing by using the --no-finalize mode. This halts the orchestration before the automated commit step, allowing manual inspection of the verified implementation.

What is the best way to manage context drift across spec, implement, and review phases?

The best way to manage context drift is using orchestrated phase-by-phase subagents. This architecture-neutral approach isolates each phase with a clean context and branch checkpointing, ensuring structured and deterministic progress.