Drive one already accepted engineering or product objective to its requested terminal. Use when completion matters more than a plan. Do not use to choose what to do next from a backlog.
Installs into .claude/skills of the current project.
Are you the author of Drive To Delivery?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-drive-to-delivery)
---
name: drive-to-delivery
description: "Drive one already accepted engineering or product objective to its requested terminal. Use when completion matters more than a plan. Do not use to choose what to do next from a backlog."
---
# Drive To Delivery
Local, landed, released, deployed, and live are distinct facts. Do not poll unchanged external state. Do not become the semantic owner of other people's artifacts. A plan that keeps growing is not delivery.
The repository's declared documentation contract wins. Place each durable fact in one writable home and link to it; do not start a second status dashboard. A missing heading is not a defect. A second writable destination is.
Open [documentation placement](references/documentation-placement.md) when the objective writes or places product documentation.
Use `bound-request-scope` when the objective is still mixed. Use `select-next-work` to pick from a backlog. Use `maintain-product` for live harm.
