Daily Prompt Pack: Remote Operations – Turn Chaos Into One SOP System

Every remote founder I know hits the same wall: the playbook lives in someone’s head, not in a document. So here’s how I drag it out. Three prompts that turn messy tribal knowledge into a working operations system you run today, not next quarter.

[Claude]

You’re my ops lead. I pasted 40 Slack threads, Loom links, and a 12-page Google Doc holding our client onboarding steps. Read all of it, then output one markdown master SOP: each numbered step, the owner role, the tool used, and the exact trigger that starts it. Flag every missing handoff or unclear owner. End with a list of the five steps most likely to break if anyone quits. Output as a single file.

[ChatGPT]

Acting as my remote ops analyst, take the 15 recurring tasks from my daily async standup log and rank them by how much time each steals per week. Build a table with columns: task, owner, weekly hours, bottleneck, and a 20-word fix for each. Then rewrite the standup log so it asks for blockers and owners, not just status updates. Output both the table and the new log template.

[Cursor]

In this repo, create OPS/STARTUP.md with a one-page remote ops runbook. Use the existing .env.example and README to infer our stack. The runbook must list: how to spin up the dev environment, the exact command to deploy, where logs live, and the first three things to check on a fresh incident. Reference real filenames only. Output the file path and a 5-line summary of decisions you made.

Full archive of daily packs at aicofounderstack.com/tag/prompt-pack.