auto

Orchestrate a software delivery workflow from raw requirement to green pull request.

88|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/heliohq/ship --skill auto-heliohq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto
Source: https://github.com/heliohq/ship/tree/main/skills/auto
Command: npx skills add https://github.com/heliohq/ship --skill auto-heliohq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of coordinating an end-to-end software delivery run by turning a raw requirement into a structured, gated path from planning to a green pull request.

Core Features & Use Cases

  • Full Workflow Orchestration: Drives the complete Ship pipeline across design, development, E2E testing, review, QA, refactor, and handoff.
  • Phase-Aware Execution: Starts fresh or resumes from disk-backed state so long-running delivery work can continue reliably after interruptions.
  • Production Delivery Control: Useful when an agent needs to carry a feature from initial requirement through validation, fixes, and final handoff with explicit quality gates.

Quick Start

Use the auto skill to run the full Ship workflow for my requirement and deliver the feature through design, implementation, testing, review, QA, refactor, and handoff.

Frequently Asked Questions about auto

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

FAQPage Schema
How do I orchestrate an end-to-end software delivery workflow from a raw requirement?

End-to-end software delivery workflow orchestration drives a raw requirement through design, development, E2E testing, code review, QA, refactor, and handoff phases to produce a green pull request.

Can I resume a software delivery workflow after an interruption?

You can resume interrupted software delivery workflows using disk-backed state, which preserves stage-aware execution so long-running feature work continues reliably across phases without restarting.

How do quality gates work within code review and QA orchestration?

Quality gates validate each phase of the delivery workflow by enforcing gated validation across design, development, E2E testing, review, QA, refactor, and handoff before progression.

What is the best way to automate the handoff stage of a feature delivery pipeline?

Automating feature delivery handoff requires a stage-aware orchestration pipeline that applies gated validation across preceding phases like development, QA, and refactor before completing the final pull request.

Does this delivery workflow orchestration require any external dependencies?

This delivery workflow orchestration operates with no external dependencies, using disk-backed state to manage stage-aware execution and gated validation across the entire software delivery pipeline.

When should I not use an orchestrated end-to-end delivery pipeline?

An orchestrated end-to-end delivery pipeline is not suited for isolated tasks or minor fixes that skip the full cycle of design, E2E testing, QA, refactor, and handoff phases.