Guide and verify

Some changes are not yours to make. The system has no API you may write to, the credentials are not yours, the change is legally or organisationally the human's, or the safe boundary of the task says a person clicks and you only read. In every one of those cases the deliverable is the same: a runbook a person can follow, plus proof that following it worked.

The failure this skill prevents is the vague handover — "remove that field from the forms and the views" — which reads as complete, sends the person hunting through a UI, and ends with nobody able to say whether it is done. The cure is measurement on both ends and a step shape tight enough to follow while tired.

The boundary comes first

Before anything else, settle who acts. If the change is the human's, print the steps and stop. Do not do it for them, do not do "just the easy half", and do not quietly widen your access to finish it. A boundary that you cross once stops being a boundary.