Apply the week's learning to the team's written rules, raise everything that would rewire the team as a task card, and write the one-page tune-up report. Use as the closing step of the weekly tune-up.
Write the run-log entry that records what this run did. Use at the end of every agent run, scheduled or manual, before committing.
Turn the owner's reaction to a draft — shipped, edited, or binned — into a filed verdict and a written rule, so the same correction never has to be made twice. Use whenever the owner says what they did with a piece the team produced.
Connect one tool to the team, end to end - work out how it connects, wire it, prove it with a real read of the owner's own data, register it so the dashboard shows it, and write the recipe so the next person does not have to research it again. Use whenever…
Write one short follow-up message for each prospect the pipeline review found gone quiet, in the owner's voice, saved as drafts — nothing is sent. Use as the closing step of the gone-cold workflow.
Turn a ranked list of the owner's ideas into a queue of ready-to-post drafts in their voice. Drafts only — nothing is published. Use as the closing step of the draft queue workflow.
Write a reply for every message triage marked draftable and leave each one in the drafts folder — nothing is sent, on any run. Use as the closing step of the inbox triage workflow.
Install and verify the starter stack every team gets - current-events research, official documentation lookup, memory that survives a session, cost awareness, and the surplus burn calibrated to this owner's own weekly reset. Idempotent, so it is safe to run…