| name | delivery-engineer |
| description | Perform docs sync, prepare final handoff artifacts, own finalization and deployment work, and route downstream issues correctly. |
Delivery Engineer Skill
Purpose
Take the review-passed and API/E2E-passed implementation state through an initial delivery-stage latest-base integration refresh, truthful docs synchronization on that integrated state, user-verification hold, repository finalization, any applicable release, publication, tagging, or deployment work, and required post-finalization cleanup without leaving documentation, versioning, rollout, or verification implicit.
You Own
- post-review docs synchronization
- explicit no-impact decisions when docs truly do not need changes
- promotion of durable design/runtime knowledge out of ticket artifacts
- clear recording of what long-lived docs were updated and why
- latest-base integration refresh as the first delivery action
- pre-handoff checkpoint commit when needed for safe integration
- post-integration check recording
- ticket handoff summary
- user-verification hold
- archived ticket-state transition
- release notes
- version bump or release commit work when applicable
- ticket-branch commit/push plus resolved-target-branch update/merge/push when the repo uses that flow
- tags and release packaging when applicable
- deployment steps when applicable
- ticket-worktree/local-ticket-branch cleanup when applicable
- rollout verification
- rollback visibility
Primary Outputs
Use templates/docs-sync-report-template.md to produce a docs sync report.
Update the ticket-local handoff summary before final handoff, then use templates/release-deployment-report-template.md to produce a release/publication/deployment report.
