From shipyard
Executes implementation plans by dispatching builder agents per task with spec compliance and code quality reviews. Use for independent tasks or triggers like 'build this' or 'execute the plan'.
npx claudepluginhub lgbarn/shipyard --plugin shipyardThis skill uses the workspace's default tool permissions.
<!-- TOKEN BUDGET: 300 lines / ~900 tokens -->
Executes complete implementation plans in controlled batches: loads and critically reviews plan, semantically selects/dispatches agents per task, handles blockages, requests code reviews between batches.
Executes written implementation plans using fresh subagents per task with TDD cycles, mandatory code reviews, and quality gates before proceeding.
Executes written implementation plans: loads and critically reviews them, runs tasks in dependency order with parallel dispatch, separate worker-validator subagents, and verifies completion.
Share bugs, ideas, or general feedback.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Execute implementation plans by dispatching fresh builder agents per task, with two-stage review after each: spec compliance review first, then code quality review. Can also run as batch execution with human checkpoints.
Core principle: Fresh agent per task + two-stage review (spec then quality) = high quality, fast iteration.
digraph when_to_use {
"Have implementation plan?" [shape=diamond];
"Tasks mostly independent?" [shape=diamond];
"Stay in this session?" [shape=diamond];
"Agent-driven execution" [shape=box];
"Batch execution with checkpoints" [shape=box];
"Manual execution or brainstorm first" [shape=box];
"Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
"Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
"Tasks mostly independent?" -> "Stay in this session?" [label="yes"];
"Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
"Stay in this session?" -> "Agent-driven execution" [label="yes"];
"Stay in this session?" -> "Batch execution with checkpoints" [label="no - parallel session"];
}
Agent-Driven Mode (preferred):
For each task, dispatch a fresh builder agent:
digraph process {
rankdir=TB;
subgraph cluster_per_task {
label="Per Task";
"Dispatch builder agent" [shape=box];
"Builder asks questions?" [shape=diamond];
"Answer questions, provide context" [shape=box];
"Builder implements, tests, commits, self-reviews" [shape=box];
"Dispatch spec reviewer agent" [shape=box];
"Spec reviewer confirms code matches spec?" [shape=diamond];
"Builder fixes spec gaps" [shape=box];
"Dispatch code quality reviewer agent" [shape=box];
"Code quality reviewer approves?" [shape=diamond];
"Builder fixes quality issues" [shape=box];
"Mark task complete" [shape=box];
}
"Read plan, extract all tasks, create via TaskCreate" [shape=box];
"More tasks remain?" [shape=diamond];
"Dispatch final reviewer for entire implementation" [shape=box];
"Use shipyard:git-workflow to complete" [shape=box style=filled fillcolor=lightgreen];
"Read plan, extract all tasks, create via TaskCreate" -> "Dispatch builder agent";
"Dispatch builder agent" -> "Builder asks questions?";
"Builder asks questions?" -> "Answer questions, provide context" [label="yes"];
"Answer questions, provide context" -> "Dispatch builder agent";
"Builder asks questions?" -> "Builder implements, tests, commits, self-reviews" [label="no"];
"Builder implements, tests, commits, self-reviews" -> "Dispatch spec reviewer agent";
"Dispatch spec reviewer agent" -> "Spec reviewer confirms code matches spec?";
"Spec reviewer confirms code matches spec?" -> "Builder fixes spec gaps" [label="no"];
"Builder fixes spec gaps" -> "Dispatch spec reviewer agent" [label="re-review"];
"Spec reviewer confirms code matches spec?" -> "Dispatch code quality reviewer agent" [label="yes"];
"Dispatch code quality reviewer agent" -> "Code quality reviewer approves?";
"Code quality reviewer approves?" -> "Builder fixes quality issues" [label="no"];
"Builder fixes quality issues" -> "Dispatch code quality reviewer agent" [label="re-review"];
"Code quality reviewer approves?" -> "Mark task complete" [label="yes"];
"Mark task complete" -> "Extract micro-lesson (best-effort)";
"Extract micro-lesson (best-effort)" -> "More tasks remain?";
"More tasks remain?" -> "Dispatch builder agent" [label="yes"];
"More tasks remain?" -> "Dispatch final reviewer for entire implementation" [label="no"];
"Dispatch final reviewer for entire implementation" -> "Dispatch auditor for security review";
"Dispatch auditor for security review" -> "Critical security findings?" [shape=diamond];
"Critical security findings?" -> "Builder fixes security issues" [label="yes"];
"Builder fixes security issues" -> "Dispatch auditor for security review" [label="re-audit"];
"Critical security findings?" -> "Dispatch simplifier for complexity review" [label="no / user defers"];
"Dispatch simplifier for complexity review" -> "High priority simplifications?" [shape=diamond];
"High priority simplifications?" -> "Builder implements simplifications" [label="user chooses fix"];
"Builder implements simplifications" -> "Dispatch simplifier for complexity review" [label="re-check"];
"High priority simplifications?" -> "Use shipyard:git-workflow to complete" [label="no / user defers"];
}
Micro-lesson (best-effort): After marking complete, extract one line: what surprised you, what failed first, or what you'd do differently. Append to
.shipyard/phases/{N}/MICRO-LESSONS.mdas- [PLAN-{W}.{P} Task {T}] <takeaway>. Pass the file contents to the next builder agent as context. If no clear takeaway, skip silently. Metrics Collection (best-effort): Also check agent output for<!-- context: ... -->. If found, append to.shipyard/phases/{N}/AGENT-METRICS.md:{ISO timestamp} | {agent-type} | {task-label} | turns={N} | compressed={yes|no} | complete={yes|no}. Skip silently if missing.
Batch Mode (separate session):
Default: First 3 tasks per batch.
For each task:
When batch complete:
Based on feedback: apply changes if needed, execute next batch, repeat until complete.
Stage 1: Spec Compliance Review
Stage 2: Code Quality Review
IMPORTANT: Always complete spec compliance before code quality. Wrong order wastes time reviewing quality of code that doesn't meet spec.
After the final reviewer approves the entire implementation, run these quality gates:
Dispatch an auditor agent (subagent_type: "shipyard:auditor") with:
model_routing.security_audit (default: sonnet). See docs/PROTOCOLS.md for details.If CRITICAL findings exist:
After the audit, dispatch a simplifier agent (subagent_type: "shipyard:simplifier") with:
model_routing.simplification (default: sonnet). See docs/PROTOCOLS.md for details.Present findings with options:
After quality gates pass:
AGENT-METRICS.md exists, review for patterns and include a "Context Health" paragraph in the phase summary. Then announce: "I'm using the git-workflow skill to complete this work."This section applies when running in a Claude Code Agent Teams context.
When Shipyard created the team via /shipyard:build team mode:
When Shipyard is running inside someone else's team:
In solo mode (neither team-lead nor team-member), this section has no effect — standard subagent dispatch applies.
STOP executing immediately when:
Ask for clarification rather than guessing.
Builder agents should:
<!-- context: turns={tool calls made}, compressed={yes|no}, task_complete={yes|no} -->Never:
If builder asks questions:
If reviewer finds issues:
If agent fails task:
Required workflow skills:
Agents should use: