delivery-executor

v0.1.2

Claude Code side of the delivery process: execute a Delivery HandOff in one repo (plan, implement, deploy+verify, review docs, move plan stages) and print a Delivery Report.

Claude Code1 Skill

By Oleksandr IeremchukLicense: MIT0 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes: Claude Code
Parsed components: 1 skill or MCP entry
Source updated: Sep 28, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install delivery-executor for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install delivery-executor@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/oleksandr-ieremchuk/digiteam-cowork-marketplace

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/delivery-executor/.

Plugin files

plugins/delivery-executor/

├── .claude-plugin/plugin.json
└── skills/executing-delivery-handoff/SKILL.md

Included Skills1

executing-delivery-handoffskills/executing-delivery-handoff/SKILL.md

Use in Claude Code when the user pastes a "Delivery HandOff — <slug> — repo: <name>" block from Cowork — normally as the argument of this skill's own slash command, /delivery-executor:executing-delivery-handoff, which is the block's first line — or says "run this handoff", "here's the handoff", "execute the delivery handoff", "print the delivery report", "move the plan to ongoing/done/documented", and equivalents in the user's language. You are the single-repo executor in a multi-repo delivery process: you verify the repo and plan stage match the requested phase, run exactly that phase (write the plan, execute it, deploy + verify, review docs, or move the plan to documented), keep the plan-stage folders truthful with git, and finish by printing a Delivery Report in the exact format Cowork parses. Never widen scope beyond the HandOff.

Plugin manifests1

plugins/delivery-executor/.claude-plugin/plugin.json

{
  "name": "delivery-executor",
  "version": "0.1.2",
  "description": "Claude Code side of the delivery process: execute a Delivery HandOff in one repo (plan, implement, deploy+verify, review docs, move plan stages) and print a Delivery Report.",
  "author": {
    "name": "Oleksandr Ieremchuk"
  },
  "repository": "https://github.com/oleksandr-ieremchuk/digiteam-cowork-marketplace",
  "license": "MIT",
  "keywords": [
    "delivery",
    "handoff",
    "report",
    "claude-code",
    "plan-stages"
  ]
}

Browse the “delivery” tag →

agent-harness-skills

by Agent Harness Skills contributors

Reusable skills for building agent-ready repository harnesses.

Codex5 Skills

1.1kUpdated 6 days ago

review-suite

by Lev Nikolaevich

Independent plan and delivery reviews with evidence-based verdicts.

CodexAgent Plugins2 Skills

557Updated last month

source-control

by Melodic Software

Git and GitHub delivery workflow: /commit (Conventional Commits + Co-authored-by trailer via safe heredoc mechanics), /pull-request (prep, create, CI monitoring, review-comment triage, merge, CI-log fetch), /babysit-prs (self-pacing fleet loop, safe by default; opt-in worker/autopilot tiers add gate-checked merge and thread resolution behind a deterministic Python engine), /babysit-loop (the loop-lane merge lane: a standing or drain loop that invokes babysit-prs per cycle, configured through repo-scoped babysit_loop_* keys on the layered source-control.md seam, with merge authority human-only until the target repo's tracked config adopts the lane, a gate-proven C2-mechanical baseline once adopted, and standing merge-rung raises binding from the team-tracked layer only, with one named exception, where an invocation line explicitly typing both the autopilot tier keyword and the dedicated raise argument --merge c3-this-run widens that single invocation's merge authority up to C3 behind a fresh independent frontier-tier resolver, while C4-structural and C5-untrusted-provenance stay unconditionally human-merge), /worktree (create, status, cleanup, audit for parallel-session isolation), /setup (check the effective commit-subject / PR-title convention merged across its config layers and the babysit-prs config, or apply, which interviews the repo and writes the convention config to a chosen layer), and /resolve-conflicts (intent-first merge/rebase conflict resolution with a semantic-conflict sweep, never --abort). The commit-subject / PR-title convention is configurable via a source-control.md config written by a re-runnable setup skill, layered across a ~/.claude user-global file, the tracked team file, and a gitignored .claude/source-control.local.md personal overlay merged per key; Conventional Commits is the default when no convention is declared.

Claude Code7 Skills

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[delivery-executor on Agent Plugins Marketplace](https://pluginsmp.com/plugins/delivery-executor)