ship
v0.3.1An agent-routed harness for end-to-end software product development.
by HelioMIT88updated 1 month ago
Source
git clone https://github.com/heliohq/shipClone the source, then follow the repository's marketplace instructions for your runtime. The repository root is the plugin root.
Layout
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/arch-design/SKILL.md├── skills/auto/SKILL.md├── skills/design/SKILL.md├── skills/dev/SKILL.md├── skills/e2e/SKILL.md├── skills/handoff/SKILL.md├── skills/qa/SKILL.md├── skills/refactor/SKILL.md├── skills/review/SKILL.md├── skills/use-ship/SKILL.md├── skills/write-docs/SKILL.md└── .mcp.json
Skills11
System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).
Run Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for explicit /ship:auto, auto pipeline requests, or end-to-end delivery.
Plan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.
Implement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first.
Add durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.
Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.
Static code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA.
Route ambiguous software-delivery requests to the smallest useful Ship workflow: one skill, a phase bundle, or /ship:auto. Use at session start, when the user asks how to use Ship, or when they say build/check/ship without a phase.
Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision.
MCP servers1
- command
- codex
- args
- mcp-server
Manifests2
{
"name": "ship",
"version": "0.3.1",
"description": "An agent-routed harness for end-to-end software product development.",
"author": {
"name": "Helio",
"url": "https://www.helio.im/"
},
"homepage": "https://www.helio.im/",
"repository": "https://github.com/heliohq/ship",
"license": "MIT",
"keywords": [
"agent",
"coding",
"planning",
"qa",
"debugging",
"refactoring",
"orchestrator",
"workflows",
"ship",
"software-delivery"
],
"skills": "./skills/",
"mcpServers": "./.mcp.json",
"hooks": "./hooks/codex-hooks.json",
"interface": {
"displayName": "Ship",
"shortDescription": "Agent-routed software delivery workflows for coding agents",
"composerIcon": "./assets/icon.svg",
"longDescription": "Use Ship to choose the right delivery route for a task: standalone skills, grouped quality/build phases, or the full raw-requirement-to-PR flow with design, implementation, E2E, review, QA, refactor, and handoff.",
"developerName": "Helio",
"category": "Coding",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"websiteURL": "https://www.helio.im/",
"privacyPolicyURL": "https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement",
"termsOfServiceURL": "https://docs.github.com/en/site-policy/github-terms/github-terms-of-service",
"defaultPrompt": [
"Choose a Ship route with /ship:use-ship",
"Plan this change with /ship:design",
"Review my current diff with /ship:review"
],
"brandColor": "#0F766E",
"screenshots": []
}
}{
"name": "ship",
"description": "An agent-routed harness for end-to-end software product development",
"version": "0.3.1",
"author": {
"name": "Helio",
"url": "https://www.helio.im/"
},
"homepage": "https://www.helio.im/",
"repository": "https://github.com/heliohq/ship",
"license": "MIT",
"keywords": [
"agent",
"coding",
"planning",
"qa",
"debugging",
"refactoring",
"orchestrator",
"workflows"
]
}