First, make sure you can trust it
Before you let go, all four of these should hold:
- You know what good looks like: you did it once, or watched it done once.
- It has the tools you’d use: a verification skill, logs.
- Every step can prove itself: it stops when it falls short.
- Repeated mistakes now have checks: you’ve read a few transcripts.
Write bedtime instructions
/pstack:poteto-mode I'm going to bed. In a fresh worktree off main, migrate every caller to the new parser.
Done means: no old callers left, every parser fixture passes, and the old API is deleted.
Keep a decision log. You don't need to ask me before committing.
/loop until done. If you've been stuck for hours and truly can't go on, stop and write down why.What each sentence does:
- I’m going to bed: keep going, don’t ask me.
- Done means: it checks this every round.
- A fresh worktree: a separate working folder, away from your own work.
- Don’t need to ask before committing: it won’t sit waiting for your OK.
- /loop until done: it keeps checking whether it’s done (built into Cursor and Claude Code).
- If stuck, stop and write why: stopping beats eight hours of busywork.
What it does all night
Before bed
- Write a done condition
- A new worktree off main
- Keep a decision log
- If stuck, stop and say why
Overnight, each round
- Check whether it's done
- Make one small change
- Verify it
- Commit if it helped, drop it if not
One line in the decision log per round
In the morning
- /pstack:show-me-your-work
- Read “needs attention” first
- Then the lines it points to
In the morning: read “needs attention” first
/pstack:show-me-your-work Walk me through what you did last nightWhat you get: a summary. Before handing it back, a model from another family reads the log and adds a “needs attention” section. Read that section first, then the lines it points to.
The log is decisions.tsv (or .audit/<task-name>.tsv when several tasks share a folder). By default it stays on your machine.
Just want progress? Type /pstack:ketchup in that chat. It tells you what changed and what’s waiting on your call.
Several jobs in one night
/pstack:poteto-mode Autopilot these five changes, but don't merge. I'll merge them myself in the morning.| What you have | Which approach | In the morning |
|---|---|---|
| Many unrelated PRs | Autopilot-full | Verified ones merged |
| Same, you merge | Autopilot-stack | A row of verified PRs |
| A multi-day project | Orchestrate | A coordinator assigning work |
Stuck?
I'm not comfortable letting it commit on its own.
Leave out “you don’t need to ask me before committing”, or use Autopilot-stack so it stops once things are verified.
I woke up and it had been going in circles.
Most likely the done condition wasn’t firm enough. Use /pstack:reflect to record the lesson, and /pstack:correct to turn repeated mistakes into checks.
I want to stop it partway.
Tell it “pause” or “I’m going offline”. It wraps up the current step and writes a resume note. A new chat can pick up from there.
Before moving on, check
✓ All ticked — on to the next step.