# Drive To Delivery

> 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.

- Skill: `sylphxai/drive-to-delivery` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sylphxai/drive-to-delivery`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sylphxai/drive-to-delivery/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: SylphxAI (https://skillmd.com/u/sylphxai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sylphxai/drive-to-delivery

---


# 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.