deliver-change

Files (2)

• SKILL.md
• LICENSE.txt · references/

SKILL.md (first lines)

# Deliver a change

1. Establish the requested destination: local handoff, proposed change, merge, or
   release. Preserve existing authorization without assuming a broader destination.
2. Inspect the final artifact and evidence. Confirm verification covers its current
   content and dependencies; changes to either require affected checks to be rerun.
3. Resolve blocking findings and disclose remaining limitations. For consequential
   landing decisions, seek independent verification when available and state gaps.
4. Present what changed, why, the verification evidence, and any operational steps.
   For authorized publication, follow the project's conventions and protect unrelated
   work. Process dependent changes in order; stop at an unverified dependency.
5. Read back external state after an action. Distinguish proposed, queued, published,
   merged, and deployed results. A successful submission is not proof of completion.
6. If watching completion was requested, bound the watch by the requested goal and
   duration. Report a stalled or failed action with evidence rather than expanding
   authority or retrying indefinitely.

Done when the requested destination is confirmed, or a precise blocker explains
why it was not reached. The handoff points to the actual result and its evidence.

Adapted from pstack; [license and attribution](references/LICENSE.txt).

From wcygan/agent-skills, MIT.

More from wcygan/agent-skills