Daily Prompt Pack: Remote Operations – Run your startup from anywhere with a repeatable ops system

Ops breaks when one person holds all of it in their head. I’ve watched it happen on small teams — the lead goes on PTO and suddenly nobody knows what’s shipping next week. These prompts force that tribal knowledge out where the rest of the team can actually read it.

I keep my own wiki in Notion, so the templates below lean that way. Swap in Confluence if that’s your thing. The prompts don’t care.

One caveat worth mentioning: the output is only as useful as what you feed in. Vague roles and tools in, vague playbook out. Spend five minutes listing them up front or you’ll just be rewriting the model’s first draft.

[Claude]

You are a remote operations lead. Given my team’s roles, time zones, and current tools below, build an async communication playbook. Output: a decision tree for when to use Slack vs email vs a doc vs a meeting, a default response-time SLA per channel, and a weekly async update template each person fills in. Format as a table, then a one-page rulebook I can paste into our wiki.

[ChatGPT]

Act as a remote ops consultant. Design a weekly operating cadence for a 5-person distributed startup. Output a day-by-day schedule: which async updates land when, the one standing meeting (with agenda and time limit), and the metrics each person reports. Then give me a Monday kickoff template and a Friday wrap template, each under 10 lines, copy-pasteable into Notion.

[Cursor]

Build a remote ops runbook in this repo. Read the README and the scripts folder, then create a markdown runbook that documents: how to run each recurring task, which command to use, who owns it, and the expected output. Add a checklist at the top for a new hire to onboard in one day. Save it to docs/runbook.md and link every script it references.

Full archive at aicofounderstack.com/tag/prompt-pack.