shipit

Plugin shipit from marketplace shipit in lbarroeta/shipit. Commands read from the repo's manifest — today.

Skills (16)

• code-handoff

  Use when shipit artifacts must be delivered — branch, commit, push, ready-for-review PRs and tracker review status by default; tracker comments, review-thread replies and issue creation only when `handoff.allow` in `.shipit/config.json` opts into them. Runs after `task-create`, `code-plan`, final `s

• code-implement

  Use when an approved shipit plan must be executed, verified, and prepared for QA. Runs the repo's own verified commands from `.shipit/config.json`. Do not use to redesign scope, and not for git or PR delivery — that is `code-handoff`.

• code-plan

  Use when planning, scoping, estimating, or breaking down a ticket, issue, bug, or feature request into an implementable contract. Works in the current checkout by default; isolated worktrees are opt-in via `worktree.enabled` or a `--worktree` flag. Do not use for implementation, and not for git or P

• code-review

  Use when an implemented shipit change must be reviewed before context sync and delivery — after `code-implement`, or as `run`'s review stage. Runs the ponytail plugin's `ponytail-review` against the diff, plus the plan and repo contract. Read-only. Do not use to fix code (`code-implement`), resolve

• design-system

  Use to bootstrap or update a repo's design contract — interviews the user in plain language, inspects existing styles, tokens and components, proposes a design, and records the approved decisions in `.shipit/design-system.md` and `.shipit/rules/design.md` so agents know which colors, components and

• doctor

  Use to check whether this machine and repo have what shipit needs — git, GitHub CLI, tracker, graph tool, prose compression, docs lookup — reported by tier with the exact fix command and its cost. `--fix` installs the safe ones after one confirmation.

• init

  Use to set a repo up for shipit in whatever state it is in — new, already documented, initialized, or carrying a legacy `.sdd/` contract. Detects stack, verified commands, layers, test patterns, tracker and existing documentation from evidence, writes the `.shipit/` contract without duplicating the

• pr-fix

  Use when an open pull request has review comments, red CI or merge conflicts. Triages each item as a senior engineer in the detected stack — which comments apply, which do not and why, the proposed fix per red check, and whether the PR can merge — then stops for approval before any edit. Scope with

• product-discovery

  Use when the user has a product idea or a running app and no PRD yet ("I have an idea", "let's write the PRD", "start a new project"). Interviews the user in the chat and writes `.shipit/product/prd.md`. Not for MVP scoping (`product-mvp-cut`), tickets (`task-create`) or code.

• product-mvp-cut

  Use when a PRD exists and the user needs to decide what ships first, or to classify a story added later ("cut the MVP", "what goes in v1", "add this story to the MVP"). Reads `.shipit/product/prd.md`, proposes the cut in the chat, and writes `.shipit/product/mvp.md`. Not for writing the PRD (`produc

• retro

  Use after a session or a `shipit:run` to propose improvements to the agent's environment — graph, verified commands, checks, rules, steering files, access, ticket quality — most severe first, each as an exact patch applied only on your yes. Never touches product code.

• run

  Execute one or more existing issues or cards from their IDs or URLs through shipit context sync, planning, implementation, code review, final sync and handoff, using native subagents with stage-specific models; several cards run in parallel, each in a worktree run creates. Resume the same task or pr

• status

  Use to see every in-flight shipit task at once — worktree, plan, branch, PR state, tracker state — and to clean up worktrees and plans whose PR is merged. Read-only unless `--prune` is passed.

• sync

  Reconcile an initialized repository's Shipit context with current sources before planning or after implementation. Update affected contracts and documentation, preserve human decisions, report conflicts, and migrate older configuration. Use init for setup and `.sdd/` migration, and design-system for

• task-create

  Use when a need, bug, feature or chore must become a clear tracker ticket or an epic with independently understandable children. Works as a senior project manager would — surveying the board for duplicates and overlapping work before drafting, then placing the ticket in its outcome, epic and depende

• task-next

  Use to recommend the next executable task from the configured live tracker as a senior project manager would — reviewing the whole board, finishing before starting, and following the dependency path from the most urgent outcome — considering project relevance, current Goal, priority, active cycle, e

Subagents (5)

• run-builder

  Execute and validate a shipit run plan, returning its implementation report to the coordinator without delivery.

• run-delivery

  Deliver a validated shipit run report and reconcile interrupted delivery, under the repository handoff allow-list.

• run-planner

  Plan an existing issue for the shipit run coordinator. Return a plan artifact and blockers; never implement or deliver.

• run-reviewer

  Review a validated shipit run implementation with ponytail-review and the repo contract, returning a verdict to the coordinator without editing code.

• run-sync

  Reconcile Shipit context before planning or after implementation and return evidence to the run coordinator.

Similar plugins