---
name: change-delivery
description: Deliver scoped project changes with clear ownership, safe execution, and accurate handoff. Use when planning, implementing, reviewing, publishing, or summarizing changes to software, design, documentation, configuration, data, or project operations.
---

# Change delivery

## Work within the requested scope

Inspect the current state and read applicable project guidance before changing anything. Preserve unrelated user work. Make reasonable, reversible implementation decisions inside the agreed scope; request direction before expanding into a materially different product, integration, or external action.

Use direct, maintainable changes instead of speculative features or broad rewrites. Keep configuration, documentation, tests, and implementation aligned. Avoid destructive operations unless their exact target and authority are clear.

## Complete the delivery path

For a change request, implement the agreed work and verify it in proportion to risk. For a publication request, complete the real release path rather than describing a local build as deployed. Treat a successful control-plane operation as incomplete until the relevant public or user-facing outcome has been checked.

## Hand off precisely

Lead with the outcome. State what changed, why, files affected, behaviour changes, and verification. Clearly separate completed work, local-only work, published work, and remaining work.