Paste a six-step Chief of Staff rule so updates replace old instructions instead of stacking them, archive superseded files with your approval, and keep one source of truth before usage balloons.
You keep refining routines and wonder why usage climbs after every "improvement."
A standing replace-don't-add process plus optional monthly audit proposal—no silent deletes.
Open your Chief of Staff bot.
Paste the six-step update rule: replace don't add, find conflicts, archive old versions only with approval, keep one source of truth, verify what loads, report the change.
Ask it to propose a monthly instruction audit but not schedule it yet.
On the next routine edit, confirm it replaced the old rule instead of stacking.
Approve any archive moves it proposes.
What's good: the prompt forces replace, conflict search, archive-with-approval, verify-what-loads, and a change report. The catch: the bot still needs your OK before archiving or scheduling the monthly audit.
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About