shipyard

Plugin shipyard from marketplace shipyard in lgbarn/shipyard. Commands read from the repo's manifest — 1 month ago.

Skills (25)

• shipyard-codex-orchestration

  Use when running any multi-step Shipyard workflow under Codex — build, audit, plan, ship, review, research, or map. Explains how Shipyard's parallel-agent workflows degrade to inline sequential execution in Codex, and routes intent to the right workflow skill. Trigger when the user says "build the p

• shipyard-map

  Use when performing brownfield analysis on an existing codebase under Codex — onboarding to a new project, generating codebase documentation, or understanding legacy code. Trigger when the user says "map this codebase", "help me understand this code", "document this project", "I just inherited this

• shipyard-research

  Use when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase under Codex. Trigger when the user says "research X", "what are our options for", "evaluate these libraries", "what's the best approach to", or before p

• shipyard-review

  Use when reviewing code under Codex — verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Trigger when the user says "review this", "review the implementation", "does this match the plan", "check the code quality", or after a Shipy

• shipyard-ship

  Use when delivering or releasing a completed Shipyard phase under Codex — final verification, pre-ship security audit, documentation, and release. Trigger when the user says "ship it", "ship this phase", "release this", "we're done — finalize", or "run the shipyard ship workflow". This is the Codex

• shipyard-state

  Use to inspect or manage Shipyard project state under Codex — show status, resume a previous session, cancel/pause in-progress work, or roll back to a checkpoint. Trigger when the user says "shipyard status", "what's the status", "resume", "continue where we left off", "cancel", "pause this", "roll

• code-simplification

  Finds and removes duplication, dead code, over-engineering, and AI-generated bloat such as verbose error handling and redundant type checks. Use after implementing features, before claiming a phase is complete, when reviewing AI-generated code, or when code feels overly complex. Also use when a patt

• documentation

  Generates and updates code docs, README files, API docs, and architecture documentation. Use when a feature with public interfaces lacks docs, when documentation is incomplete or outdated, or before shipping any phase. Also use when adding breaking changes or complex algorithms, or when a public fun

• git-workflow

  Manages branches, worktrees, atomic commits, and branch completion by merge, PR, preserve, or discard. Use when starting feature work that needs a branch or an isolated workspace, making commits during development, or finishing a development branch. Also use when the user says "set up worktree", "cr

• import-spec-file

  Imports a handwritten spec document into Shipyard in place of brainstorming. Use when a freeform spec, requirements, or design document already exists.

• import-spec

  Imports a spec-kit feature spec into Shipyard in place of brainstorming. Use when a spec-kit feature directory with spec.md exists.

• infrastructure-validation

  Validates infrastructure-as-code with tool chains and checks for common mistakes. Use when working with Terraform (.tf, .tfvars), Ansible (playbooks, roles, inventory), Docker (Dockerfile, docker-compose.yml), Kubernetes (manifests, Helm charts), or CloudFormation. Also use when running terraform pl

• lessons-learned

  Extracts reusable lessons from completed work. Use when a phase or milestone is complete, before shipping, or when reflecting on finished work. Also use when the user says "what did we learn", "capture lessons", "retrospective", "wrap up", "ship this phase", or "done with this phase". A phase must n

• parallel-dispatch

  Dispatches concurrent agents for independent tasks. Use when 2 or more tasks can proceed without shared state or sequential dependencies, such as multiple test files that fail with different root causes or multiple subsystems that are broken independently. Applies when tasks touch different files an

• security-audit

  Audits code for OWASP Top 10 issues, secrets in code (API keys, passwords, tokens), dependency vulnerabilities, IaC security, Docker hardening, and supply chain risks. Use when working with code that handles user input, authentication, authorization, or secrets. Also use when adding or updating depe

• shipyard-brainstorming

  Explores user intent, requirements, and design through Socratic dialogue before implementation. Must be used before any creative work, such as creating features, building components, adding functionality, or modifying behavior. Also use when the user says "I want to add", "let's design", "what if we

• shipyard-debugging

  Investigates root cause systematically before any fix is proposed. Use when encountering any bug, test failure, unexpected behavior, or error message. Also use for tracebacks, exceptions, "not working" complaints, build failures, performance problems, or integration issues, and whenever the next ste

• shipyard-executing-plans

  Executes a written implementation plan with agents. Use when a written plan is ready to execute, in the current session or a separate one. Also use when the user says "build this", "implement this", "execute the plan", or "run the plan", or when a loaded plan file has independent tasks suitable for

• shipyard-handoff

  Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress. Use when the user says "handoff", "save context", or "I'm done for now", or when a long session ends and its state should be recorded.

• shipyard-tdd

  Enforces test-driven development, with a failing test before any production code. Use when implementing any feature or bugfix, before writing implementation code. Also use when touching test files (*.test.*, *.spec.*, *_test.go), when plan tasks have tdd="true", or when the user says "test first", "

• shipyard-testing

  Guides test design with AAA structure, DAMP naming, mock boundaries, and the testing pyramid. Use when writing tests, structuring test suites, choosing test boundaries, or fixing test quality issues such as flakiness, over-mocking, or brittle tests. Also use when choosing between unit, integration,

• shipyard-verification

  Requires fresh verification evidence before any claim that work is complete, fixed, or passing. Use before committing, creating PRs, or moving to the next task. Also use when a status report contains words like "should", "probably", or "seems to", or expresses satisfaction ("Great!", "Done!") before

• shipyard-writing-plans

  Breaks a spec, requirements, or design into an implementation plan with file paths and verification commands. Use for any multi-step task before touching code. Also use when the user says "plan this", "break this down", "create tasks", or "decompose this feature", when a task needs more than 2-3 ste

• shipyard-writing-skills

  Applies test-driven development to creating and editing skills. Use when creating, editing, or improving a skill, editing any SKILL.md file, writing skill descriptions, or debugging why a skill does not activate. Also use when the user says "create a skill", "write a skill", "new skill", "improve th

• using-shipyard

  Explains how to find and use Shipyard skills and commands, and requires a Skill tool call before any response, including clarifying questions. Use at the start of any conversation, or when the user asks "what should I do", "help me", "how do I use shipyard", or "where do I start". Also use when it i

Slash commands (25)

• /shipyard:audit

  On-demand security audit — OWASP, secrets, dependencies, IaC security

• /shipyard:brainstorm

  Explore requirements through Socratic dialogue and capture project definition

• /shipyard:build

  Execute plans using fresh subagents with review gates

• /shipyard:cancel

  Pause in-progress work with a checkpoint

• /shipyard:debug

  Investigate bugs and failures with systematic root-cause analysis

• /shipyard:doctor

  Check Shipyard plugin health and dependencies

• /shipyard:document

  On-demand documentation generation — API docs, architecture updates, user guides

• /shipyard:help

  Show help for Shipyard commands and skills

• /shipyard:init

  Initialize Shipyard project settings and directory structure

• /shipyard:issues

  View and manage deferred issues tracked across sessions

• /shipyard:map

  On-demand codebase analysis — map technology stack, architecture, quality, or concerns

• /shipyard:move-docs

  Move codebase documentation between .shipyard/codebase and docs/codebase

• /shipyard:plan

  Plan a phase of work (creates roadmap if needed)

• /shipyard:quick

  Execute a small task with Shipyard guarantees

• /shipyard:recover

  Diagnose and recover from interrupted or corrupted state

• /shipyard:research

  On-demand domain research — evaluate technology options, investigate ecosystem choices

• /shipyard:resume

  Restore context from a previous session and continue

• /shipyard:review

  On-demand code review — review current changes, a diff range, or specific files

• /shipyard:rollback

  Revert to a previous Shipyard checkpoint

• /shipyard:settings

  View or update Shipyard workflow settings

• /shipyard:ship

  Finish and deliver completed work

• /shipyard:simplify

  On-demand simplification review — detect duplication, dead code, unnecessary complexity, AI bloat

• /shipyard:status

  Show project progress and route to next action

• /shipyard:verify

  On-demand verification — run tests, check acceptance criteria, validate phase completion

• /shipyard:worktree

  Manage git worktrees for isolated feature development

Subagents (10)

• architect

  Use this agent when creating roadmaps, decomposing plans into tasks, making architecture decisions, or breaking down requirements into executable work. Examples: <example>Context: The user is initializing a new project and needs a roadmap. user: "Create a roadmap for building this application" assis

• auditor

  Use this agent for comprehensive security and compliance analysis across all changes in a phase or milestone. Covers OWASP Top 10, secrets detection, dependency vulnerabilities, IaC security, and supply chain risks. Examples: <example>Context: A phase build is complete and needs security review befo

• builder

  Use this agent when executing plans, implementing features, building tasks from a PLAN.md, or running TDD implementation cycles. This is the primary implementation agent. Examples: <example>Context: A plan has been created and is ready for execution. user: "Build the authentication phase" assistant:

• debugger

  Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and produces ROOT-CAUSE.md with evidence chain and remediation plan. Examples: <example>Context: A test suite is failing after a recent commit and the cause is unclear. user: "Figure o

• documenter

  Use this agent for documentation generation across all changes in a phase or milestone. Generates API docs, architecture updates, and user-facing documentation. Examples: <example>Context: A phase build is complete and needs documentation updated. user: "Generate documentation for the completed phas

• mapper

  Use this agent when performing brownfield analysis on an existing codebase, onboarding to a new project, generating codebase documentation, or understanding legacy code. Examples: <example>Context: The user wants to understand an existing codebase they are joining or inheriting. user: "I need to und

• researcher

  Use this agent when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase. Examples: <example>Context: The user is planning a new phase and needs to understand the best technology choices. user: "We need to add real

• reviewer

  Use this agent when performing code review, verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Examples: <example>Context: A plan has been fully executed by the builder and needs review. user: "Review the authentication implementa

• simplifier

  Use this agent to review cumulative code changes across a phase for duplication, unnecessary complexity, dead code, and AI-generated bloat that individual task reviewers can't detect. Examples: <example>Context: A phase build is complete, all reviews passed, and the code needs a whole-picture simpli

• verifier

  Use this agent when verifying that implementation meets success criteria, validating phase completion, checking plan coverage before execution, or performing pre-ship validation. Examples: <example>Context: A phase has been fully built and reviewed, and needs final verification before moving on. use

Hooks (5)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/state-read.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/marketplace-sync.sh

• TeammateIdle

  ${CLAUDE_PLUGIN_ROOT}/hooks/teammate-idle.sh

• TaskCompleted

  ${CLAUDE_PLUGIN_ROOT}/hooks/task-completed.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/stop.sh

Similar plugins