Free to read · no account needed

16 min · agents

From one-shot to scheduled runs

Goal: graduate a manual agent job to a repeatable schedule without losing checkpoints.

Best for: weekly briefs or cleanups you already run successfully by hand.

A schedule is a multiplier. It multiplies good loops and bad ones. Earn the right to automate by succeeding manually with logs and red-lines intact. Do not schedule what you have not run manually three times. Keep human checkpoints for send/delete. See Checkpoints and Team playbook.

Why beginners skip this

Scheduling before the job is stable feels advanced until a 3am silent failure or a surprise send. Three clean hand-runs plus a kill switch beat optimism. Mid-week cost shows up as rework, not as a missing bookmark.

Step 1 — Prove the manual loop

Checklist: Done met three times, log rows clean, red-lines never skipped.

Here are 3 run-log rows for the same job:
[paste]
Is it ready to schedule? Yes/No with 5 bullets.
Be harsh about near-miss sends.
Example

Filled prompt

Job: Friday status email to eng manager from my notes folder.
I have only ONE clean manual run logged.
Write Auto vs Manual in 5 lines. If manual runs <3, insist Manual and list what to log next two Fridays before any schedule.

What good output looks like

  • Done boxes for “graduate a manual agent job to a repeatable schedu” are explicit and checkable
  • Allow-list tools only; never-do lines honored
  • Stops before send/delete without human gate
  • Pass/fail: Plan→Act one→Check visible for agents-from-one-shot-to-scheduled
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Step 2 — Schedule the safe part only

Auto: gather + draft. Manual: approve send/publish. Write that split explicitly on the one-pager.

Split this job into Auto vs Manual steps for scheduling:
Job: [paste]
Anything that leaves the building (email, post, delete) stays Manual.
Example

Filled prompt

Job: Monday 9:00 competitor headline skim via read-only web.
Manual runs logged: 0 clean (two messy experiments).
Write Auto vs Manual in 5 lines. Insist Manual. List what "clean" means before any cron.

What good output looks like

  • Allow-list tools only; never-do lines honored
  • Stops before send/delete without human gate
  • Pass/fail: Plan→Act one→Check visible for agents-from-one-shot-to-scheduled
  • Done boxes for “graduate a manual agent job to a repeatable schedu” are explicit and checkable

Step 3 — Add a kill switch

Know how to disable the schedule in two clicks. Document it before enabling. If you cannot find the off switch, you are not ready.

Write kill-switch instructions (≤6 steps) for a scheduled agent job in [product].
Beginner clicks. End with “confirm disabled.”
Example

Filled prompt

≤6 steps to disable our Monday 9:00 brief schedule.
Product UI is generic: Settings → Automations → pause.
Include who to tell (business owner).

What good output looks like

  • Counts clean manual runs honestly
  • Chooses Manual when count < 3
  • Lists what to log on the next two Fridays
  • Keeps send on ask even in a future Auto design

Three manual wins

Schedule only after three clean manual runs with logs. Near-miss sends block automation.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

One more pass

Re-read your Save-this-card line. If it is vague, rewrite it until a stranger could apply it.

Red flag

Scheduling before three clean hand-runs; no kill switch; scheduled job can send externally without a human gate—disable it.

Save this card

Card: three clean hand-runs · kill switch · failure contact. Schedule only after the three. Keep this beside the tool; refuse to start if a box is blank.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Write Done (checkboxes) and the human gate on paper before any run for “graduate a manual agent job to a repeatable.” Allow-list tools; leave send/delete off. Guide: agents-from-one-shot-to-scheduled. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week: pick one agent job you already ran by hand three clean times. Schedule it once; keep irreversible actions on ask-every-time. Log the schedule id and a dated pass/fail on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed agents-from-one-shot-to-scheduled, put 25 minutes on the calendar and redo once.

Pitfalls

PitfallFix
Scheduling after one lucky runThree manual wins first
Auto-send on day oneDraft-only automation
No kill switch docWrite it before enabling
Schedule without an ownerFill team playbook first
Example

Filled prompt

Temptation: skip the habit for agents-from-one-shot-to-scheduled to “save five minutes.”
Job still: graduate a manual agent job to a repeatable
Do the smallest correct pass: Done visible · one checkable artifact · Unknowns labeled [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: the artifact + the refuse-line you said aloud.

What good output looks like

  • Names the shortcut you refused (specific to agents-from-one-shot-to-scheduled)
  • Still delivers a checkable artifact for “graduate a manual agent job to a repeatable”
  • Unknowns labeled; draft-only respected
  • Pass/fail: refuse-line written and dated (agents-from-one-shot-to-scheduled #4)

Practice now

Live card: run one agent checklist item on a real job for “From one-shot to scheduled runs”—artifact path on Save (Asia/Shanghai).

Today: log three clean hand-runs of the same job. Only if all three pass, draft a schedule plus a kill switch and a failure contact. Date the log (Asia/Shanghai).

Today card (copy) — agents-from-one-shot-to-scheduled: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Three clean manual runs before any schedule; irreversible stays on ask—prove it on a real artifact, or skip the badge

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

Checkpoints · Team playbook · Logging what matters · Failure modes and retries · Plan → act → check

Pair with today: open the first Next link (agents-human-in-the-loop-checkpoints) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start