delivery-engineer

Synchronize docs, finalize branches, and execute release and deployment handoffs.

2|1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/AutoByteus/autobyteus-agents --skill delivery-engineer-autobyteus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-engineer
Source: https://github.com/AutoByteus/autobyteus-agents/tree/main/agent-teams/software-engineering-team/agents/delivery-engineer/skills/delivery-engineer
Command: npx skills add https://github.com/AutoByteus/autobyteus-agents --skill delivery-engineer-autobyteus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It closes the gap between a reviewed, tested implementation and a truthful, finalized delivery by enforcing docs synchronization, latest-base integration, user verification, and clean release or deployment steps. ## Core Features & Use Cases - Docs Synchronization: Updates long-lived project docs against the final integrated implementation state, records no-impact decisions, and promotes durable design knowledge out of ticket artifacts. - Integration & Finalization Workflow: Refreshes the ticket branch against the latest tracked remote base, reruns checks, waits for explicit user verification, then commits, merges, and pushes the finalization target branch. - Release & Deployment Reporting: Produces structured docs sync and release/deployment reports covering versioning, tags, release notes, rollout verification, rollback criteria, and post-finalization cleanup. - Use Case: After a code review and API/E2E pass on a feature branch, use this Skill to sync the docs, hold for user verification, merge into the target branch, tag the release, and clean up the ticket worktree. ## Quick Start Take the reviewed implementation through docs sync, user verification, branch finalization, and release using the delivery workflow.

Frequently Asked Questions about delivery-engineer

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

FAQPage Schema
How do I finalize a ticket branch after code review passes?▼

Refresh the ticket branch against the latest tracked remote base, rerun at least one executable check, update the handoff summary, and wait for explicit user verification. Then commit and push the ticket branch, update the target branch, merge, and push.

How to keep project documentation in sync with implementation?▼

Use the integrated, reviewed implementation state as the primary truth and update long-lived docs to match final behavior. Record durable design knowledge promoted from ticket artifacts and explicitly document any no-impact decision when docs need no changes.

What happens if the remote base advances before final merge?▼

Delivery protects uncommitted delivery-owned edits, re-integrates the ticket branch with the advanced base, and reruns required checks. If the user-facing handoff state materially changes, docs and the handoff summary are updated and renewed verification is obtained.

When should a delivery be blocked instead of finalized?▼

Block delivery when docs cannot be updated truthfully, integration conflicts arise, post-integration checks fail, or finalization steps error. Record the blocker classification and recommended recipient, such as implementation or solution design, in the delivery report.

Does this workflow handle release notes and deployment cleanup?▼

Yes, release notes are created before user verification and passed into the release or publication path when applicable. After finalization, ticket worktrees and local branches are cleaned up when the recorded target makes that safe.