Plugin · Claude Code · Productivity

Lgbarn Shipyard

Shipyard is a Claude Code plugin for the Build phase that runs a structured idea-to-production lifecycle with parallel agents, audits, and quality gates.

by lgbarn · github.com/lgbarn/shipyard

Run a gated solo project from first idea through ship with parallel Claude agents, audits, and validation instead of ad-hoc prompting.

50
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install lgbarn-shipyard@lgbarn/shipyard
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:lgbarn/shipyard") and the paste-ready config with skillselion.get_install_config("plugin:lgbarn/shipyard").

About

What it does

lgbarn Shipyard is a Claude Code plugin marketplace entry that packages a structured project lifecycle for solo builders and small teams who want agent-assisted development without losing control. Instead of treating each session as a one-off chat, Shipyard frames work from early concept through production with discipline: parallel agents can take scoped tasks while quality gates force review, security checks, and validation before code is treated as done. That makes it especially useful when you are shipping a SaaS, CLI, or agent-heavy product and need repeatable rituals rather than heroics. Install it when your bottleneck is process—skipped tests, fuzzy scope, or agents racing ahead without audit—not when you only need a single API hook. It complements task-specific skills and MCP tools by acting as the backbone that sequences when those tools run. Complexity is advanced because you must internalize the lifecycle model and gate semantics to get value.

Highlights

  • End-to-end lifecycle from idea to production with explicit phases and gates
  • Parallel agent workflows for faster implementation with review boundaries
  • Built-in auditing, security, and validation checkpoints before you ship
  • Systematic software delivery keywords: review, infrastructure, lifecycle, validation
  • Single bundled Shipyard plugin focused on disciplined agent-led builds

Why builders use it

Solo builders using Claude Code often ship inconsistently because agents lack a shared lifecycle, gates, and parallel work boundaries.

After you add Shipyard, projects move through defined phases with validation and review so production-bound work stays disciplined instead of chaotic.

At a glance

  • Type - Plugin in Productivity.
  • Adoption - 0 installs, 50 stars, 0 votes.

FAQ

Who is lgbarn Shipyard for?

It is for solo and indie builders who use Claude Code to ship real software and want systematic phases, parallel agents, and validation instead of unstructured agent sessions.

When should I use Shipyard?

Use it when starting or steering a multi-week product—especially when you need audits, security review, and gates between idea, build, and production.

How do I add Shipyard to my agent?

Register the lgbarn/shipyard Claude Code plugin from the marketplace or repo, enable it in Claude Code, then follow the plugin’s lifecycle commands for your project.

Discussion

Comments

Share how you use lgbarn-shipyard, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.