ship-fleet

Survey, plan, and execute product backlog features in dependency order.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of delivering features across your product backlog, ensuring that all remaining work is systematically surveyed, planned, and executed.

Core Features & Use Cases

  • Backlog Survey: Classifies and categorizes all remaining feature work in a repository.
  • Orchestrator Plan: Generates a comprehensive plan-and-ledger (ORCHESTRATOR.md) for the feature delivery.
  • Concurrent Execution: Manages up to 8 concurrent ship-feature runs in dependency order.
  • Dependency Management: Ensures that features are executed in the correct order based on dependencies.
  • Use Case: When you want to ensure that all remaining features in your product backlog are delivered systematically and efficiently.

Quick Start

Use the ship-fleet skill to orchestrate the feature delivery for your product backlog.

Frequently Asked Questions about ship-fleet

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

FAQPage Schema
How do I orchestrate feature delivery across a product backlog?

Orchestrating feature delivery involves surveying remaining backlog items, generating a plan-and-ledger, and executing features concurrently. This skill systematically manages up to 8 concurrent feature runs in dependency order to streamline product backlog delivery.

What is the best way to manage dependencies during concurrent feature execution?

Managing dependencies during concurrent execution requires structuring the pipeline so features run in the correct order. This skill uses an orchestrator plan to map dependencies and coordinates up to 8 concurrent runs to ensure correct execution order.

How does backlog survey and categorization work for feature delivery?

Backlog surveying classifies and categorizes all remaining feature work in a repository. This process ensures that every feature is accounted for before generating a comprehensive execution plan and ledger for the delivery pipeline.

Can I run multiple features concurrently without breaking dependency order?

Yes, you can run multiple features concurrently while respecting dependency order. The skill manages up to 8 concurrent feature runs and uses robust error handling to ensure dependencies are resolved before dependent features execute.

What do I need to generate an orchestrator plan for feature delivery?

Generating an orchestrator plan requires a repository with remaining feature work to survey. The skill analyzes the backlog, classifies features, and produces a comprehensive `ORCHESTRATOR.md` plan-and-ledger to coordinate the delivery pipeline.

Why does feature delivery fail when backlog items are not surveyed first?

Feature delivery fails without surveying because dependencies and categorizations are unknown. Surveying the backlog first ensures all remaining work is classified, allowing the orchestrator to generate a structured plan and execute features in the correct dependency order.