shipwright-delivery

Plugin shipwright-delivery from marketplace shipwright in vebg/shipwright. Commands read from the repo's manifest — 19 days ago.

Skills (13)

• balance

  Cost balance of the workspace — every task with its status, group (feature or priority band) and USD cost, a header with the total spent and statistics (by status, average/median per done task, most expensive, forecast for the remaining tasks) and the budget lines from shipwright.json when set. Use

• design

  Start the frontend-designer on the ready design parts (static-first UI) after the owner's go, then inspect its screenshots and evidence and close or return each design part. Use when ready tasks name the frontend-designer.

• develop

  Start the fullstack-developer on the next eligible tasks after the owner's go — returned tasks (verification failed) first, then ready backend and integration tasks — and record the hand-over. Use when ready implementation tasks exist.

• doctor

  Check the machine and the workspace before agents run — Python, Git, Node, Claude Code, the kit files and validator, the code repositories, the Hindsight runtime/server/hooks, context-mode, guard hooks, ignore lines, and the mobile/evidence tools (Xcode, adb, Flutter, .NET, ImageMagick, ffmpeg). Use

• owner

  The owner's checklist — everything the owner must do that agents never do: versions to release since the last deployed one, environment/configuration lines, migrations, store steps, "For the owner" sections from evidence, open questions with their defaults, and HANDOFF's "waiting on the owner" items

• plan

  Run a planning pass as the planner — ingest new or changed requirement sources, update the spec, scope, architecture, decisions, diagrams, traceability and the dependency-ordered backlog, record open questions and validate the index. Use after requirements arrive or change, or when the owner asks to

• questions

  The open-questions table for the owner — every question in docs/QUESTIONS.md §1 and every awaited input in §3 with its default in force, what it blocks and a one-line way to answer. Use when the owner asks "what do you need from me?" or before a planning session.

• release

  Set up or run the kit's release bookkeeping — one shared product version tagged in every code repository per verified task, a release note per version, compatibility rules after the first public release. Use when the owner wants versioning/tagging or a release note, or when the planner needs to reco

• resume

  Resume a Shipwright workspace — read the handoff and the backlog, recheck interrupted work, and propose the next batch (returned tasks first, then design parts awaiting inspection, then hand-overs awaiting the tester, then the next ready tasks). Use at the start of a session in an existing workspace

• start

  Guided entry point of the Shipwright. Runs the discovery interview (product, users, surfaces, inspiration links/videos/apps, technologies already decided, constraints, brand, working agreement), collects the few decisions the kit needs, scaffolds the workspace (optionally with Hindsight memory and c

• status

  Report the state of a Shipwright workspace — backlog counts by status and verification, next ready tasks, open questions, blockers, Git status per repository and the token cost so far. Use when the owner asks where things stand.

• verify

  Start the manual-tester on the tasks handed over with verification pending, then read its evidence, replan follow-ups and update the handoff. Use after a developer hand-over.

• workflow

  The Shipwright's shared delivery protocol — task states and index fields, the manual verification flow, the static-first UI work split, design and screenshot workflow, engineering discipline, multi-repository rules and session sizing. Load when an agent needs the exact rule for a hand-over, a status

Subagents (5)

• frontend-designer

  Front-end design owner for every surface (web pages and hosts, native mobile and tablet apps). Delivers the static presentation only — markup, styles and theming, screen/widget/theme files, motion, every UI state as a Development-only design route with hardcoded sample values, UI strings, assets, de

• fullstack-developer

  Backend owner (API, realtime, persistence, auth, contracts, clients, build and release preparation) and the whole front-end integration that connects frontend-designer's static UI to real data; fixes every returned task, including designer-built UI, without redesigning it. Self-checks builds and run

• manual-tester

  Manually verifies tasks handed over by fullstack-developer (verification pending) by running the real API, apps and browsers against each acceptance criterion, including negative, authorization and concurrency checks; records evidence with real screenshots and sets the task done or returns it with d

• planner

  Main-session lead of the Shipwright. Turns requirements into traceable scope, architecture, decisions and dependency-ordered tasks; orchestrates frontend-designer, fullstack-developer and manual-tester one at a time; closes static design parts by inspection; keeps docs/HANDOFF.md current. Runs as th

• store-compliance-reviewer

  Optional pre-submission review of mobile app builds and store listings against Apple's App Store Review Guidelines and Google Play's Developer Program Policy, using the project's vetted offline analyzers plus its own rule checklist; keeps docs/store-compliance/DASHBOARD.md with a GO / GO WITH NOTES

Hooks (6)

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/session_start.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/skill_guard.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/agent_guard.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/policy_guard.py"

• SubagentStop

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/token_usage.py" --quiet || true

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/token_usage.py" --quiet || true

Similar plugins