skills.rest
heliohq
heliohqOFFICIAL
Explore all skills by this author →
WebsiteGitHub

use-ship

Route software-delivery requests to the smallest useful Ship workflow.

88|6|Updated Mar 25, 2026
Search Tags:#quality gates#software delivery#ship#agentic development#workflow routing#phase selection
One-click install
npx skills add https://github.com/heliohq/ship --skill use-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-ship
Source: https://github.com/heliohq/ship/tree/main/skills/use-ship
Command: npx skills add https://github.com/heliohq/ship --skill use-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents overusing the full Ship pipeline when a request only needs a single phase or a smaller bundle, helping agents choose the lightest workflow that still meets delivery goals.

Core Features & Use Cases

  • Workflow Routing: Decides whether a request should use one standalone skill, a phase bundle, or the full /ship:auto flow.
  • Session-Start Guidance: Helps users who ask how to use Ship, or who give vague requests like build, check, or ship without specifying a phase.
  • Delivery Scoping: Supports common paths such as planning, implementation, review, QA, refactor, handoff, and end-to-end production delivery.
  • Use Case: A user says “build this feature” and the Skill routes them to design first, then development, instead of launching the full production workflow immediately.

Quick Start

Use the use-ship skill to pick the smallest useful Ship workflow for this request and then invoke the matching phase or bundle.

Frequently Asked Questions about use-ship

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

FAQPage Schema
How do I route a software delivery request to the right workflow phase?▼

Workflow routing evaluates your software delivery request and selects the lightest appropriate Ship workflow, directing vague commands to a single standalone skill or phase bundle instead of the full pipeline.

When should I use a standalone skill instead of the full agentic development pipeline?▼

Use a standalone skill when a software delivery request only needs a single phase like planning or review, preventing overuse of the full pipeline while still enforcing evidence, tests, and artifact boundaries.

What is phase selection in software delivery workflows?▼

Phase selection determines whether a request requires a standalone skill, a phase bundle, or the full delivery flow, applying minimal repo context to enforce evidence, tests, and artifact boundaries.

How do I start a session with vague software delivery commands like build or ship?▼

Session-start guidance interprets vague commands like build, check, or ship without specified phases, routing them to the correct delivery scoping path such as design first, then development.

Can I skip quality gates for small software delivery tasks?▼

Quality gates are enforced even for small tasks, as the routing mechanism requires minimal repo context but strictly enforces evidence, tests, and artifact boundaries across all selected workflows.

Related Skills

Explore More Software Engineering Skills→
nuttarujnuttaruj
3

using-rolepod

Route software development requests into the correct workflow phase.

Community
Advanced
UncodierUncodier

makinari-rol-judge-app

Evaluate app and site flow items against standardized judging rules and evidence gates.

Community
Advanced
keshav55keshav55

autopilot

Automate end-to-end task execution with a PRD-driven plan-do-review loop.

Community
Advanced
ShaheerKhawajaShaheerKhawaja
8

auto-mode

Orchestrate a 10-phase software pipeline with stateful resume and gate-driven decisions.

Community
Advanced