task-deliver

Commits verified changes and opens a pull request after a tool-backed verification gate passes.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill task-deliver-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-deliver
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/task-deliver
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill task-deliver-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code without proof it was verified leads to broken releases. This Skill is the final phase of the taskmaster pipeline: it refuses to deliver unless the preceding verification step passed against the current working tree, then delegates the actual commit and pull request creation to the existing commit and pr-create workflows. ## Core Features & Use Cases - Verification gate: Calls the verify MCP tool with the spec slug and blocks delivery on a FAIL verdict, missing test evidence, or stale verification that no longer matches the working tree. - Delegated commit and PR creation: Reuses the commit and pr-create skills, enriching the commit message and PR body with spec context, verification results, critic verdicts, and open items. - Metrics and lessons capture: Relays the task metrics record written by the gate, stages it with the commit, updates the spec lifecycle to shipped, and optionally records a retrospective lesson. - Use Case: After finishing implementation and running task-verify on a feature branch, ask to deliver the task; the Skill checks the gate, commits the work with the metrics record, and opens a PR carrying both critic verdicts and any freshness override. ## Quick Start Deliver the finished task by committing the verified changes and opening a pull request for the current spec.

Frequently Asked Questions about task-deliver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deliver a task after verification in the taskmaster pipeline?▼

Invoke the deliver step after task-verify passes. The Skill calls the verify MCP tool gate with the spec slug, and on ALLOW it commits the changes via the commit workflow and opens a pull request via pr-create with spec and verification context.

What happens if verification is stale or failed before delivery?▼

Delivery is blocked. A stale verdict requires re-running task-verify, and only an explicit user decision permits retrying with allowStale, which is then disclosed in the PR body. A FAIL verdict can never be waived and requires fixing the failing gates first.

Can I deliver without the verify MCP tool available?▼

No. If the verify tool is unavailable, the Skill refuses to deliver rather than reading verification.md by hand, because a manual read provides no freshness check against the current working tree.

Does the pull request include critic verdicts and open items?▼

Yes. The PR body carries separate lines for the spec critic and diff critic verdicts, any refuted findings, and deferred or blocked open items from the fix cycle. A surviving diff-critic blocker causes a draft PR instead of a normal one.

What artifacts are kept after delivery?▼

The .marvin/task/ artifacts (spec, plan, verification) are preserved as documentation, and the metrics record under .marvin/metrics/ is staged and committed alongside the delivered code.