audit
On-demand security audit — OWASP, secrets, dependencies, IaC security
On-demand verification — run tests, check acceptance criteria, validate phase completion
> /plugin marketplace add lgbarn/shipyard > /plugin install shipyard@shipyard
How it fires
How this command gets triggered: by you, by Claude, or both.
/verifyContext preview
What this command does when you run it.
On-demand verification — run tests, check acceptance criteria, validate phase completion
description: "On-demand verification — run tests, check acceptance criteria, validate phase completion" disable-model-invocation: true argument-hint: "[criteria] — criteria file, phase number, or run project tests (default)"
You are executing on-demand verification. Follow these steps precisely.
<prerequisites>
Extract from the command:
1. Check if `.shipyard/` exists (optional — this command works anywhere). 2. If `.shipyard/config.json` exists, read `model_routing.validation` for model selection. 3. Otherwise, use default model: **haiku**. 4. Follow **Worktree Protocol** (see `docs/PROTOCOLS.md`) — detect worktree context.
</prerequisites>
<execution>
Assemble context per **Agent Context Protocol** (see `docs/PROTOCOLS.md`):
Dispatch a **verifier agent** (subagent_type: "shipyard:verifier") with:
</execution>
<output>
Display the verification report to the user.
If failures exist, offer follow-up: > "Would you like me to: > - Fix the failing criteria > - Run a more detailed review (`/shipyard:review`) > - Check security on the verified code (`/shipyard:audit`)"
</output>
A Claude Code plugin for structured project execution. Plan work in phases, build with parallel agents and TDD, review with security audits and quality gates, and ship with confidence.
Repo: lgbarn/shipyard
On-demand security audit — OWASP, secrets, dependencies, IaC security
Explore requirements through Socratic dialogue and capture project definition
Execute plans using fresh subagents with review gates
Investigate bugs and failures with systematic root-cause analysis