Stats
Actions
Available In
Tags
Plugin
shipyard
Turn your idea into working code — Shipyard runs Claude Code through a spec-driven agile sprint lifecycle: discuss features, plan sprints, build with TDD, review, and ship.
What's Inside
Agents14
shipyard-builder
/shipyard-builder
Executes sprint tasks by writing code with strict test-driven development (write tests first, then code). Follows acceptance criteria from task specs.
shipyard-critic
/shipyard-critic
Adversarial reviewer that challenges feature specs and sprint plans before user approval. Multi-persona critique with structured findings. Read-only — never modifies artifacts.
shipyard-discovery-scout
/shipyard-discovery-scout
Discovery analyst for /ship-discuss Phase 1.5b. Loads challenge / edge-case / NFR / failure-mode methodology references and the feature draft, returns a structured findings list. Read-only — never modifies artifacts.
shipyard-investigator
/shipyard-investigator
Deep-dive investigation agent. Receives ONE code review finding and confirms or refutes it with evidence. Reads call sites, traces data flow, checks tests. Returns a verdict.
shipyard-researcher
/shipyard-researcher
Investigates technical unknowns, codebase patterns, and external APIs. Read-only with respect to the codebase — searches and reports but never modifies code. Write tool is scoped by contract to findings docs under <SHIPYARD_DATA>/research/ only, never anywhere else. Dispatched by /ship-execute for kind: research sprint tasks (task-driven mode) and by /ship-discuss or /ship-sprint for inline technical investigation (free-form mode). Fire when a task has kind: research, or when a design decision needs tradeoff analysis, external API evaluation, or a codebase pattern scan before a sprint is planned.
Skills12
ship-backlog
/ship-backlog
View, groom, and manage the prioritized backlog sorted by RICE score. Use when the user wants to see the backlog, reprioritize features, run a grooming session, clean up stale items, declare backlog bankruptcy, or decide what to work on next.
ship-bug
/ship-bug
Report a bug or production issue with minimal ceremony. Creates a spec entry and optional fix task. Use when the user reports something broken, a defect, unexpected behavior, a regression, or needs to file a hotfix for production. Also use for --hotfix emergency production issues.
ship-debug
/ship-debug
Systematic debugging with persistent state that survives session breaks and /clear. Use when the user reports a bug, something isn't working, tests are failing, they're stuck on an error, or they want to investigate unexpected behavior. Also use when the user says 'debug', 'investigate', 'why is this broken', or 'help me fix this'.
ship-discuss
/ship-discuss
Feature discovery — from quick idea capture to full spec with acceptance criteria. Use when the user mentions a new feature, a 'what if', a 'we should also', wants to discuss requirements, brainstorm, refine an existing feature, explore what to build next, define acceptance criteria, or jot down something for later.
ship-execute
/ship-execute
Execute the current sprint by running tasks in waves with strict test-driven development (write tests first, then code). Supports solo, subagent, and team execution modes. Use when the user wants to start building, execute sprint tasks, run a specific task, apply a hotfix, or resume execution after a break.
Stats
Version1.11.0
LanguageJavaScript
Stars1
MaintenanceGood
LicenseMIT
Last Commit
Added
Safety Signals
Critical
Matches all tools
Hooks run on every tool call, not just specific ones
Caution
Executes bash commands
Hook triggers when Bash tool is used
Tags
Categories
