Ralph Overnight Builds — Progressive Curriculum Entry
A graduated path to unattended Ralph runs: start with a single bounded task, add a PROMPT.md spec file, add verification, and only then remove the human from the loop for overnight builds.
Implementation note
When to use: you are tempted by overnight Ralph runs but have not run one before — this is the curriculum that gets you there without learning each failure mode the expensive way. How it works: a staged path where each stage adds one piece of rigor. Start with a single bounded task run under supervision. Then move the task definition into a PROMPT.md spec file. Then add verification, so done is machine-checked rather than asserted. Only after all three are solid do you remove the human from the loop and let it run overnight. Each stage exercises the discipline the next one depends on. Safety: the sequencing is the safety mechanism — unattended operation is earned last, after bounded scope, a written spec, and objective verification are already proven on supervised runs. Most overnight-loop disasters trace to a skipped stage. When you do go unattended, add the standard rails: iteration caps, budget limits, sandbox, branch.
Source: Claude Code Masterclass newsletter ↗graded B · 75/100 — how grades work →
More planning loops
Implement feature X autonomously
Ralph runs until it outputs DONE, implementing the feature end-to-end over up to 20 iterations.
Ship GOALS.md phases 1-13
Implement each GOALS.md phase with tests and validation, committing and pushing after stable milestones until unblocked.
Execute roadmap phases to completion
Work through each phase in your roadmap, verify each one, run the final audit, and stop when all phases pass.