Agent Plugins Marketplace
← All plugins

shipyard

v0.67.0+codex.e65533c6e8e313c6

Artifact-driven delivery pipeline on top of GSD: deep investigation, ticket decomposition with a dependency graph, and per-ticket worktree->PR delivery babysat to green (CI + CodeRabbit/Copilot re-review). See docs/gsd_multilevel_delivery_pipeline.md.

Codex6 Skills

By Nochevnyi Serhii0 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes
Codex
Parsed components
6 skill or MCP entries
Source updated
Sep 27, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install shipyard for Codex

Installs for the current user
codex plugin marketplace add serhii-nochevnyi/shipyard
codex plugin marketplace upgrade shipyard
codex plugin add shipyard@shipyard

Paste and run these commands in a terminal with Codex. They add and refresh the shipyard catalog, then install this plugin.

Compatibility: the page URL and API slug “shipyard-3” remain stable.

  • Codex: shipyard-3@agent-plugin-marketplace → shipyard@shipyard

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/serhii-nochevnyi/shipyard

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/shipyard/.

Plugin files

plugins/shipyard/
├── .codex-plugin/plugin.json
├── skills/shipyard-bench/SKILL.md
├── skills/shipyard-decompose/SKILL.md
├── skills/shipyard-deliver/SKILL.md
├── skills/shipyard-delivery-rules/SKILL.md
├── skills/shipyard-investigate/SKILL.md
└── skills/shipyard-route/SKILL.md

Included Skills6

shipyard-benchskills/shipyard-bench/SKILL.md

Off-conveyor direct work mode for when /shipyard:deliver does not fit — implement in the CURRENT/given worktree: code, tests, local run; never create branches/worktrees/PRs, never merge/ship, and do NOT commit unless explicitly asked.

shipyard-decomposeskills/shipyard-decompose/SKILL.md

Decomposition (loop 2): ADR → GSD plan-tickets with dependencies → valid graph (Gate 2), then export to Jira. Finds undecomposed ADRs on its own. Use when the user explicitly wants an accepted design/ADR broken into tickets — it creates tickets, so invoke it deliberately, not from idle discussion.

shipyard-deliverskills/shipyard-deliver/SKILL.md

Delivery (loop 3): cold start → ticket board → scope selection → worktree/PR per ticket → babysit to green (CI + CodeRabbit/Copilot re-init). At the end of the phase — integrator. Use when tickets already exist and the user explicitly wants them shipped as PRs — it opens PRs and drives merges, so invoke it deliberately, not from idle discussion.

shipyard-delivery-rulesskills/shipyard-delivery-rules/SKILL.md

Delivery-conveyor rules for GSD planner/executor agents — plan frontmatter contract, delivery block, branch naming, scope discipline. Injected via the project-relative .shipyard/generated/gsd-delivery-rules projection; also useful when authoring or editing PLAN.md files by hand.

shipyard-investigateskills/shipyard-investigate/SKILL.md

Deep investigation (loop 1): pick up an open INV or create a new one; intake interview, research fan-out, iterative dialogue, Gate 1 → ADR. Use when a topic is unclear, needs research, or the key decisions are not made yet — before any tickets or code.

shipyard-routeskills/shipyard-route/SKILL.md

Entry router for shipyard — surface this automatically whenever a scope of work has been defined in conversation and no shipyard loop is already running. It sizes the work and routes it: large/heavy multi-ticket efforts → investigate/decompose/deliver; small changes, an existing ticket, or 'no ticket' → bench; a one-liner → inline. Read-only and advisory: it classifies and hands off, and never creates tickets, branches, PRs, or commits itself (so it is safe to trigger on its own). Triggers: a defined scope of work, 'route this', 'what should we do with this', 'here's the scope — take it', 'kick off shipyard for this', or any implement/build/fix request where the right entry is unclear.

Plugin manifests1

plugins/shipyard/.codex-plugin/plugin.json
{
  "name": "shipyard",
  "version": "0.67.0+codex.e65533c6e8e313c6",
  "description": "Artifact-driven delivery pipeline on top of GSD: deep investigation, ticket decomposition with a dependency graph, and per-ticket worktree->PR delivery babysat to green (CI + CodeRabbit/Copilot re-review). See docs/gsd_multilevel_delivery_pipeline.md.",
  "author": {
    "name": "Nochevnyi Serhii"
  },
  "repository": "https://github.com/serhii-nochevnyi/shipyard",
  "skills": "./skills/",
  "interface": {
    "displayName": "Shipyard",
    "shortDescription": "Research, plan and deliver with GSD.",
    "longDescription": "Native Codex delivery workflows with GSD plugin dependency setup, validated agents and host gates.",
    "developerName": "Nochevnyi Serhii",
    "category": "Productivity",
    "capabilities": [
      "Read",
      "Write"
    ],
    "defaultPrompt": [
      "Use Shipyard to route this task."
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[shipyard on Agent Plugins Marketplace](https://pluginsmp.com/plugins/shipyard-3)